Approved changes feed: RSS · Atom

cpe:2.3:a:boringproxy:boringproxy:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorBoringproxy (5ce4ed3e-dff4-5789-918a-4c756510f013)
ProductBoringproxy (518d6819-01e5-5968-8f01-134c6254bfc6)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-70616 vulnerable 2026-09-16 04:33:01.005560 boringproxy 0.10.0 Resource Exhaustion DoS via GET /loading endpoint
MEDIUM (6.5)
boringproxy through 0.10.0 contains a resource exhaustion vulnerability that allows any authenticated user to permanently exhaust server file descriptors, goroutines, and memory by sending requests to the GET /loading endpoint with attacker-supplied id query parameter values. Because the handler performs no map-lookup validity check and receives on a nil channel that blocks forever, with no timeout, no context cancellation, and no server-side reclamation due to absent HTTP server timeouts, each malicious request permanently holds one goroutine, one file descriptor, and approximately 50 kB of memory until the server's file descriptor limit is reached and listener Accept calls fail, halting all tunnel traffic forwarding for all users.
Published: 2026-08-05T19:37:36.081Z
Updated: 2026-08-06T18:44:57.415Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-70615 vulnerable 2026-09-16 04:33:00.258199 boringproxy 0.10.0 SSH authorized_keys Injection via Tunnel Creation
CRITICAL (9.9)
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.
Published: 2026-08-05T19:34:13.322Z
Updated: 2026-08-06T17:33:41.750Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.