CVE-2026-118781: Forge: Denial of Service via infinite loop in BigInteger.modInverse() with negative input (incomplete fix of CVE-2026-33891)

Published Oct 29, 2026
·
Updated

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used BigInteger.prototype.modInverse(), bnModInverse(), lib/jsbn.js, RSA public exponent e to process the relevant input or security decision. node-forge's bundled jsbn implementation entered an infinite loop when BigInteger.prototype.modInverse() received a negative value or modulus. An attacker who could control the RSA public exponent passed to key generation, or a direct modInverse() operand, could block the Node.js event loop at full CPU. Parsed DER, PEM, JWK, PKCS#12, X.509, and TLS values are unsigned and cannot trigger this issue. This issue is fixed in version 1.4.1.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade node-forge to a version that resolves this vulnerability.

    Fixed in 1.4.1

Event History

Oct 29, 2026
CVE Published
via MITRE·06:49 PM
Data Sourced
via MITRE·06:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Are applications that only parse common key, certificate, or TLS formats exposed?

No. Parsed DER, PEM, JWK, PKCS#12, X.509, and TLS values are unsigned and cannot trigger the infinite loop.

2

What attacker control is required to cause the denial of service?

An attacker must be able to control the RSA public exponent supplied to key generation or directly control an operand passed to modInverse(). A negative value or modulus is required to trigger the loop.

3

What happens when the issue is triggered?

The affected jsbn implementation enters an infinite loop, blocking the Node.js event loop at full CPU. This can cause denial of service for the affected process.

4

Which versions should be remediated?

The issue affects Forge versions prior to 1.4.1. Upgrade to version 1.4.1, which fixes the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203