CVE-2026-40316
RCE in OWASP BLT before 2.1.1 via PR-triggered CI workflow.
Is CVE-2026-40316 being exploited?
Not confirmed. CVE-2026-40316 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-40316?
CVE-2026-40316 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-40316?
Yes. A fix has been recorded for CVE-2026-40316. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40316 affect?
CVE-2026-40316 affects OWASP BLT <2.1.1, GitHub Actions runner. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40316?
Upgrade to 2.1.1 when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE in privileged CI environment; attacker can execute code and exfiltrate secrets via GITHUB_TOKEN.
Immediate action required
- affected<= 2.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.