# Apache Airflow vulnerable to Code Injection in the web-server context via LogTemplate table

Advisory record · `GHSA-r837-hpv7-pc2f`

- **Identifiers:** `GHSA-r837-hpv7-pc2f` · `BIT-airflow-2024-56373` · `CVE-2024-56373` · `PYSEC-2026-2355`
- **State:** Confirmed
- **Severity:** CVSS 8.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 24 Feb 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Feb 2026, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-airflow` (PyPI): affected `<2.11.1`; fixed in `2.11.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Airflow versions before 2.11.1 are vulnerable to code injection in the web-server context through the LogTemplate table. A DAG author, who already holds substantial permissions, can manipulate the Airflow 2 database to run arbitrary code on the web server when a user views historical task information. Upgrade to Airflow 2.11.1, where the log template history functionality is disabled by default; to keep using log template history, upgrade to Airflow 3 instead.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.012, the 69th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r837-hpv7-pc2f)

## Sources

- [GitHub Advisory Database: GHSA-r837-hpv7-pc2f](https://github.com/advisories/GHSA-r837-hpv7-pc2f)
- [OSV: GHSA-r837-hpv7-pc2f](https://osv.dev/vulnerability/GHSA-r837-hpv7-pc2f)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-56373>
- <https://github.com/apache/airflow/pull/61880>
- <https://github.com/apache/airflow>
- <https://lists.apache.org/thread/2vrmrhcht6g7cp5yjxpnrk2wtrncm6cy>
- <http://www.openwall.com/lists/oss-security/2026/02/23/3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r837-hpv7-pc2f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r837-hpv7-pc2f/>. Everything for agents: <https://agentprime.io/llms.txt>.