CVE-2026-111395

waiting for further signalsZero needs more public information before it can validate it.

GHSA-r5x9-822m-2crg ↗EUVD-2026-119892 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Airflow >= 3.2.0, < 3.4.0
fixed in 3.4.0
CWE-502 Deserialization of Untrusted Data
ETK-2026-3938Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/apache-airflow-core
1d 21h 14msince last run
21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h28m
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Airflow Core before 3.4.0 does not properly filter reserved serialization fields supplied in DAG-run configuration. A user permitted to start a DAG using deadline alerts with asynchronous callbacks may cause recurring scheduler crashes or unintended object reconstruction in the Triggerer.

mitigation

Upgrade apache-airflow-core to version 3.4.0 or later. Until upgraded, restrict who can trigger DAGs that use deadline alerts with asynchronous callbacks.

fixed in 3.4.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 09:18Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-09 09:18Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-111395

{
  "etk_id": "ETK-2026-3938",
  "cve_id": "CVE-2026-111395",
  "display_id": "CVE-2026-111395",
  "ghsa_id": "GHSA-r5x9-822m-2crg",
  "euvd_id": "EUVD-2026-119892",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Reserved-key deserialization flaw in Apache Airflow",
  "summary": "Apache Airflow Core before 3.4.0 does not properly filter reserved serialization fields supplied in DAG-run configuration. A user permitted to start a DAG using deadline alerts with asynchronous callbacks may cause recurring scheduler crashes or unintended object reconstruction in the Triggerer.",
  "mitigation": "Upgrade apache-airflow-core to version 3.4.0 or later. Until upgraded, restrict who can trigger DAGs that use deadline alerts with asynchronous callbacks.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Airflow",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.2.0, < 3.4.0"
      ],
      "ecosystem": "pypi",
      "fixed_versions": [
        "3.4.0"
      ],
      "package_name": "apache-airflow-core",
      "purl": "pkg:pypi/apache-airflow-core"
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.65657665,
  "t0_at": "2026-11-09T09:18:35.415000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T09:18:35.415000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T09:18:35.415000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111395"
    }
  }
}

published 2026-11-09 09:25Z
last change 2026-11-11 06:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.