CVE-2026-55629
Path traversal in Whistle proxy allows arbitrary file read.
Is CVE-2026-55629 being exploited?
Not confirmed. CVE-2026-55629 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.67% probability of exploitation in the next 30 days.
How severe is CVE-2026-55629?
CVE-2026-55629 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-55629?
Yes. A fix has been recorded for CVE-2026-55629. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55629 affect?
CVE-2026-55629 affects Whistle < 2.10.3, lib/service/service.js. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55629?
Upgrade Whistle to 2.10.3 and restrict access to the proxy.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers can read arbitrary files (e.g., /etc/passwd) via crafted GET /cgi-bin/temp/get filename, causing sensitive data disclosure.
Patch when possible
- affected< 2.10.3
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.