CVE-2026-119186

MEDIUM CVSS 5.9
Published: 2026-10-29
Modified: 2026-10-30
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-119186 is a moderate vulnerability with a CVSS score of 5.9 affecting the target software. Authentication can be bypassed allowing unauthenticated access. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge did not validate the AES-GCM tagLength option passed to start() during decryption through forge.cipher.createDecipher(). When an application derived tagLength from received data or used an unset or zero-like configuration value, a value that converted to zero together with an empty or missing authentication tag caused the calculated and supplied tags to compare as empty, so decipher.finish() accepted unauthenticated ciphertext. Applications that omit tagLength to use the 128-bit default or pass a fixed valid tag length are unaffected. This issue is fixed in version 1.4.1.

Attack Chain
1
Reconnaissance

Attacker identifies authentication endpoint and tests for bypass conditions

2
Initial Access

Attacker exploits CVE-2026-119186 authentication flaw to gain unauthorized access without valid credentials

3
Discovery

Attacker enumerates accessible resources, users, and configurations

4
Collection

Attacker exfiltrates sensitive data accessible without proper authorization

MITRE ATT&CK Techniques
T1078 Valid Accounts
Initial Access

Authentication bypass grants attacker access as legitimate user

T1548 Abuse Elevation Control Mechanism
Privilege Escalation

Bypassed auth may grant elevated or admin-level permissions

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.