Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
node-forge <1.4.1 could misrepresent trusted identifiers
published 2 days ago
Summary
If your application uses node-forge versions older than 1.4.1 and accepts identifier strings from outside sources, the library could change those strings into a different, trusted identifier when converting them to a binary format. This could allow unauthorized actions to be accepted as legitimate. Upgrade node-forge to version 1.4.1 or later to fix the issue.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Debian:13 | docker hardened images | postman-mcp | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | kyverno-policy-reporter-ui-dev | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | kyverno-policy-reporter-ui-fips-dev | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | kyverno-policy-reporter-ui-fips | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | kyverno-policy-reporter-ui | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | postman-mcp | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | sorry-cypress-director-2 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | kibana-9.4 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | kibana-9.5 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | kubeflow-pipelines-frontend | All versions |
Original advisory text
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1…
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, asn1.oidToDer() in lib/asn1.js did not range-check the first two arcs of an OID. An application that accepted an untrusted OID string, checked or authorized that string, and then encoded it with asn1.oidToDer() could emit DER representing a different, trusted OID from the one that was checked. DER parsing is not affected. This issue is fixed in version 1.4.1.
References
- https://scout.docker.com/v/DHI-iueo-2p76-bhyr-yd5s Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-118775 Vendor Advisory
- https://github.com/digitalbazaar/forge/security/advisories/GHSA-4642-5mcj-2rqw Vendor Advisory
- https://github.com/digitalbazaar/forge/commit/e56a3dde8e4e63bae566bb32546eeaf92f... Patch
- https://github.com/digitalbazaar/forge/releases/tag/v1.4.1 URL
- https://github.com/advisories/GHSA-4642-5mcj-2rqw Vendor Advisory
- https://ubuntu.com/security/CVE-2026-118775 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-118775 Vendor Advisory
Internet-facing
14 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
DHI-iueo-2p76-bhyr-yd5s · OSV
Track software like this
Free during beta