H3js h3
h3 before 1.15.9 Path Traversal via Double Decoding
h3 versions before 1.15.9 contain a path traversal vulnerability in the serveStatic utility. A double-decoding flaw allows a request path containing double-encoded dot sequences (e.g. %252e%252e) to be decoded to %2e%2e, which survives resolveDotSegments() because that function only checks for literal '.' characters. When the resulting asset ID is resolved by URL-based backends (CDN, S3, object storage), %2e%2e is interpreted as '..' per RFC 3986, enabling path traversal to read arbitrary files from the backend.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.2high · scored by CNA · CWE-22
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
h3js h3
- < 1.15.9
Fixed in 1.15.9
Mitigation
Upgrade h3 to 1.15.9 or later.
References
- Vendor advisory github.com/h3js/h3/security/advisories/GHSA-72…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.