CVE-2026-32805
Path traversal in Romeo tar extraction allows writing files outside target dir.
Is CVE-2026-32805 being exploited?
Not confirmed. CVE-2026-32805 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-32805?
CVE-2026-32805 is rated High with a CVSS score of 8.3. 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-32805?
Yes. A fix has been recorded for CVE-2026-32805. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32805 affect?
CVE-2026-32805 affects Romeo (Go coverage tool), GitHub Actions workflows using Romeo. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32805?
Upgrade to v0.2.2+; audit tar handling in CI.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can craft a tar that bypasses checks and writes outside the destination, risking overwrite of sensitive files.
Immediate action required
- affected< 0.2.2
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.