CVE-2026-70615

boringproxy 0.10.0 SSH authorized_keys Injection via Tunnel Creation

Published Aug 5, 2026 CVSS 4.0 · 8.5 High EPSS < 1% KEV · Not listed
Description
boringproxy through 0.10.0 contains a newline injection vulnerability that allows authenticated low-privileged users with tunnel-creation permission to inject arbitrary lines into the server account's SSH authorized_keys file by supplying a percent-encoded newline character in the domain parameter of the tunnel creation endpoint. Attackers can insert an unrestricted public key entry into authorized_keys to gain persistent shell access, and subsequently read cleartext credentials from the database file including all user tokens, tunnel private keys, and TLS certificates.

Analysis

AI-generated

Technical impact

Boringproxy, up to version 0.10.0, allows an authenticated low‑privileged user to inject arbitrary lines into the SSH authorized_keys file by supplying a percent‑encoded newline character in the domain parameter of the tunnel creation endpoint. This injection permits the attacker to add an unrestricted public key, creating persistent shell access; the attacker can then read cleartext credentials from the database file, exposing user tokens, tunnel private keys, and TLS certificates.

Affected Systems

The Boringproxy open‑source proxy, version 0.10.0 and earlier, is affected.

Risk and Exploitability

This vulnerability carries a CVSS score of 8.5, indicating high severity. The EPSS score is not available, so the current exploitation probability is unknown, and the KEV catalog does not list it. An attacker must first authenticate as a low‑privileged user with tunnel‑creation rights; by inserting a percent‑encoded newline (%0A) into the domain parameter of the tunnel creation endpoint, the attacker can inject arbitrary lines into the SSH authorized_keys file, thereby creating an unrestricted public‑key entry that yields persistent shell access. The attacker can then read cleartext credentials from the database, exposing all user tokens, tunnel private keys, and TLS certificates.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Boringproxy to the latest version that removes the newline injection flaw.
  • Configure the application to reject percent‑encoded newline characters (%0A) in the domain parameter of the tunnel creation endpoint and validate input strictly.
  • Restrict tunnel‑creation permissions to trusted users only, and monitor for unauthorized SSH key additions.

Generated by OpenCVE AI on August 5, 2026 at 20:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Boringproxy
Boringproxy boringproxy
Vendors & Products Boringproxy
Boringproxy boringproxy
Type Values Removed Values Added
Description boringproxy through 0.10.0 contains a newline injection vulnerability that allows authenticated low-privileged users with tunnel-creation permission to inject arbitrary lines into the server account's SSH authorized_keys file by supplying a percent-encoded newline character in the domain parameter of the tunnel creation endpoint. Attackers can insert an unrestricted public key entry into authorized_keys to gain persistent shell access, and subsequently read cleartext credentials from the database file including all user tokens, tunnel private keys, and TLS certificates.
Title boringproxy 0.10.0 SSH authorized_keys Injection via Tunnel Creation
Weaknesses CWE-93
References
Metrics cvssV3_1

{'score': 9.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.5, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H'}

Weaknesses
  • CWE-93

    Improper Neutralization of CRLF Sequences ('CRLF Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 6, 2026, 5:33 PM
Reserved
Aug 4, 2026, 8:17 PM
Status
Deferred
Published
Aug 5, 2026, 8:17 PM
Modified
Sep 24, 2026, 8:43 PM