Attack Chain

1. The attacker obtains a valid leaf certificate (e.g., a TLS certificate) that lacks both the basicConstraints and keyUsage extensions.
2. The attacker uses this leaf certificate to sign a malicious certificate for a target domain (e.g., victim.example.com). The forged certificate appears to be issued by a legitimate but compromised CA.
3. The attacker intercepts network traffic between a client and a server.
4. The attacker presents the forged certificate chain (root CA -> compromised leaf CA -> malicious certificate for victim.example.com) to the client.
5. The client application uses node-forge’s pki.verifyCertificateChain() function to validate the certificate chain.
6. Due to the missing basicConstraints and keyUsage extensions in the compromised leaf certificate, the validation process incorrectly accepts the certificate chain as valid.
7. The client establishes a TLS connection with the attacker, believing they are communicating with the legitimate server.
8. The attacker can then eavesdrop on, modify, or block the communication between the client and the server, leading to data theft, account compromise, or denial of service.

Impact

Successful exploitation of this vulnerability can lead to complete compromise of applications relying on node-forge for certificate validation. An attacker can forge certificates for any domain, allowing them to perform man-in-the-middle attacks, intercept sensitive data, and impersonate legitimate services. The number of potential victims is large, affecting any application using node-forge for custom PKI implementations, S/MIME signature verification, IoT device certificate validation, and any non-native-TLS certificate chain verification. The severity is high, as it bypasses fundamental security controls related to certificate trust.

Recommendation

• Upgrade to node-forge version 1.3.4 or later, which includes the fix for CVE-2026-33896.
• Deploy the following Sigma rule to detect the execution of node-forge with vulnerable versions to identify potentially affected systems.
• If upgrading is not immediately feasible, consider patching the lib/x509.js file in your node-forge installation with the fix suggested in the advisory.