Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
node-forge before 1.4.1 may accept wrong signature type
published 2 days ago
Summary
Versions of the node-forge library earlier than 1.4.1 can treat a certificate that declares a modern RSASSA-PSS signature as if it used the older PKCS#1 v1.5 method. This could let a certificate pass checks that specifically require the newer signature scheme, even though the signature is still created by the trusted issuer. Upgrade node-forge to version 1.4.1 or later in the listed Docker images to close the gap.
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: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 |
| Docker Hardened Images:Debian:13 | docker hardened images | postman-mcp | 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, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer's private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.
References
- https://scout.docker.com/v/DHI-plgf-63r7-4a5n-yw24 Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-118774 Vendor Advisory
- https://github.com/digitalbazaar/forge/security/advisories/GHSA-9wg5-mj3p-v49q Vendor Advisory
- https://github.com/digitalbazaar/forge/commit/c7f42614d5166a77ddf11ce174b2601b14... Patch
- https://github.com/digitalbazaar/forge/releases/tag/v1.4.1 URL
- https://github.com/advisories/GHSA-9wg5-mj3p-v49q Vendor Advisory
- https://ubuntu.com/security/CVE-2026-118774 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-118774 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-plgf-63r7-4a5n-yw24 · OSV
Track software like this
Free during beta