CVE-2026-24480
RCE via vulnerable QGIS GitHub Actions workflow before fix.
Is CVE-2026-24480 being exploited?
Not confirmed. CVE-2026-24480 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.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-24480?
CVE-2026-24480 is rated High with a CVSS score of 8.7. 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-24480?
Yes. A fix has been recorded for CVE-2026-24480. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-24480 affect?
CVE-2026-24480 affects QGIS, GitHub Actions (pull_request_target), base repository credentials. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24480?
Update to fixed version; audit CI to avoid pull_request_target.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
PR workflow could execute untrusted PR code with base-repo credentials, enabling arbitrary commands with elevated privileges.
Patch when possible
- affected< 76a693cd91650f9b4e83edac525e5e4f90d954e9
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.