CVE-2026-32847
Unauthenticated path traversal exposes files via encoded path on SPA catch-all route.
Is CVE-2026-32847 being exploited?
Not confirmed. CVE-2026-32847 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-32847?
CVE-2026-32847 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-32847?
Not known from our data. No patch reference has been recorded for CVE-2026-32847, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What should I do about CVE-2026-32847?
Monitor and plan patch when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Exposes sensitive files (SSH keys, TLS certs, secrets) by reading arbitrary files through crafted path segments.
Monitor only
- affected<= 1.2.0
- affected<= c991dc22e67958a031f2e20595128a6a5fbd8f3d
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.