CVE-2026-70615
Authenticated newline injection allows SSH key planting and credential theft in boringproxy.
Is CVE-2026-70615 being exploited?
Not confirmed. CVE-2026-70615 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.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-70615?
CVE-2026-70615 is rated High with a CVSS score of 8.5. 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-70615?
Not known from our data. No patch reference has been recorded for CVE-2026-70615, 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 does CVE-2026-70615 affect?
CVE-2026-70615 affects boringproxy <= 0.10.0, boringproxy server (authorized_keys), systems using boringproxy-managed tunnels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70615?
Upgrade boringproxy when patch available, restrict tunnel-creation rights, rotate SSH keys/tokens/certs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated low-privileged user can inject a newline to add SSH authorized_keys, gain persistent shell, and exfiltrate DB tokens, tunnel private keys, and TLS certs.
Immediate action required
- affected<= 0.10.0
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.