# Apache Airflow's Task SDK rebuilt a \`Callback\` object from serialized data by re-running its constructor, which imports the module named by the stored callback path. Because \`SyncCallback\` is itsel... Advisory record · `GHSA-2qjv-p2gc-mjg2` - **Identifiers:** `GHSA-2qjv-p2gc-mjg2` · `BIT-airflow-2026-67587` · `CVE-2026-67587` · `PYSEC-2026-3708` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** No - **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html) - **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) - **Published:** 12 Aug 2026 - **Updated:** 15 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 12 Aug 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `apache-airflow` (PyPI): affected `>=3.3.0, <3.3.1`; fixed in `3.3.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Airflow versions 3.3.0 up to but not including 3.3.1 are affected. A Dag author, who can control a task instance's next_kwargs through the task execution API, can cause an arbitrary module to be imported inside the scheduler process during the awaiting_input timeout sweep. Upgrade to apache-airflow 3.3.1 or later; tightening allowed_deserialization_classes does not mitigate this issue. Written 1 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.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from OSV - **CISA KEV:** Not listed. - **EPSS:** 0.0061, the 49th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 12 Aug 2026, 15:32 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-67587) - 12 Aug 2026, 16:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-67587) - 31 Oct 2026, 14:08 UTC: First seen by agentprime - 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3708) ## Sources - [GitHub Advisory Database: GHSA-2qjv-p2gc-mjg2](https://github.com/advisories/GHSA-2qjv-p2gc-mjg2) - [OSV: GHSA-2qjv-p2gc-mjg2](https://osv.dev/vulnerability/GHSA-2qjv-p2gc-mjg2) - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .