{"items":[{"id":"NVI-00008948","kind":"vulnerability","title":"Forge: Denial of service in TLS record processing via call stack exhaustion","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hqq3-7jhf-c5jx","CVE-2026-119187"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1b7956a3ee54ff8443dcc97c485f4466"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.4.1 for node-forge. Confirm the publisher’s latest guidance.","source_ids":["sr-960f3b5379022e3809c2c7402de484d8"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:01:54.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-46ca39d5c7ee5feb2d27dbf55f2bd787"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.415%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35799. Missing scores are unknown.","source_id":"sr-1b7956a3ee54ff8443dcc97c485f4466"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-46ca39d5c7ee5feb2d27dbf55f2bd787","url":"https://github.com/advisories/GHSA-hqq3-7jhf-c5jx","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-hqq3-7jhf-c5jx","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-960f3b5379022e3809c2c7402de484d8","url":"https://github.com/advisories/GHSA-hqq3-7jhf-c5jx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hqq3-7jhf-c5jx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:57:10.795Z"},{"id":"sr-1b7956a3ee54ff8443dcc97c485f4466","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-119187","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.268Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-46ca39d5c7ee5feb2d27dbf55f2bd787"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nConnections created with `forge.tls.createConnection()` processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and `process()` throws `RangeError: Maximum call stack size exceeded`, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1.\n\n### Details\n\nIn `lib/tls.js`, `c.process()` reads one record and passes it to `_update()`, which calls the handler for the record type from `ctTable`. Every handler (`tls.handleHeartbeat`, `tls.handleApplicationData`, `tls.handleHandshake` for fragmented messages, `tls.handleHelloRequest` and the other handshake handlers) ends by calling `c.process()` again to continue with the next buffered record, or the next message in the same record. Each record therefore adds `process` → `_update` → handler to the call stack. In Node.js 24, about 2,300 eight-byte records (under 20 KB) in one chunk are enough for `process()` to throw `RangeError: Maximum call stack size exceeded`.\n\n`ctTable` maps heartbeat records to `tls.handleHeartbeat` in every client and serv","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-960f3b5379022e3809c2c7402de484d8"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nConnections created with `forge.tls.createConnection()` processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and `process()` throws `RangeError: Maximum call stack size exceeded`, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1.\n\n### Details\n\nIn `lib/tls.js`, `c.process()` reads one record and passes it to `_update()`, which calls the handler for the record type from `ctTable`. Every handler (`tls.handleHeartbeat`, `tls.handleApplicationData`, `tls.handleHandshake` for fragmented messages, `tls.handleHelloRequest` and the other handshake handlers) ends by calling `c.process()` again to continue with the next buffered record, or the next message in the same record. Each record therefore adds `process` → `_update` → handler to the call stack. In Node.js 24, about 2,300 eight-byte records (under 20 KB) in one chunk are enough for `process()` to throw `RangeError: Maximum call stack size exceeded`.\n\n`ctTable` maps heartbeat records to `tls.handleHeartbeat` in every client and serv","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-04T18:04:03.098Z","source_updated_at":"2026-10-30T23:01:54.000Z","source_disclosed_at":"2026-10-30T23:01:54.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008948","kind":"vulnerability","title":"Forge: Denial of service in TLS record processing via call stack exhaustion","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-hqq3-7jhf-c5jx","CVE-2026-119187"],"plain_summary":"GitHub lists this reviewed advisory for node-forge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-46ca39d5c7ee5feb2d27dbf55f2bd787"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 1.4.1 for node-forge. Confirm the publisher’s latest guidance.","source_ids":["sr-960f3b5379022e3809c2c7402de484d8"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:01:54.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-46ca39d5c7ee5feb2d27dbf55f2bd787"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-46ca39d5c7ee5feb2d27dbf55f2bd787","url":"https://github.com/advisories/GHSA-hqq3-7jhf-c5jx","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-hqq3-7jhf-c5jx","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-960f3b5379022e3809c2c7402de484d8","url":"https://github.com/advisories/GHSA-hqq3-7jhf-c5jx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-hqq3-7jhf-c5jx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:57:10.795Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-46ca39d5c7ee5feb2d27dbf55f2bd787"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nConnections created with `forge.tls.createConnection()` processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and `process()` throws `RangeError: Maximum call stack size exceeded`, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1.\n\n### Details\n\nIn `lib/tls.js`, `c.process()` reads one record and passes it to `_update()`, which calls the handler for the record type from `ctTable`. Every handler (`tls.handleHeartbeat`, `tls.handleApplicationData`, `tls.handleHandshake` for fragmented messages, `tls.handleHelloRequest` and the other handshake handlers) ends by calling `c.process()` again to continue with the next buffered record, or the next message in the same record. Each record therefore adds `process` → `_update` → handler to the call stack. In Node.js 24, about 2,300 eight-byte records (under 20 KB) in one chunk are enough for `process()` to throw `RangeError: Maximum call stack size exceeded`.\n\n`ctTable` maps heartbeat records to `tls.handleHeartbeat` in every client and serv","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-960f3b5379022e3809c2c7402de484d8"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nConnections created with `forge.tls.createConnection()` processed received TLS records recursively, one stack level per record. A peer can send one chunk of thousands of small records, such as heartbeat records, which are accepted before the handshake, and `process()` throws `RangeError: Maximum call stack size exceeded`, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1.\n\n### Details\n\nIn `lib/tls.js`, `c.process()` reads one record and passes it to `_update()`, which calls the handler for the record type from `ctTable`. Every handler (`tls.handleHeartbeat`, `tls.handleApplicationData`, `tls.handleHandshake` for fragmented messages, `tls.handleHelloRequest` and the other handshake handlers) ends by calling `c.process()` again to continue with the next buffered record, or the next message in the same record. Each record therefore adds `process` → `_update` → handler to the call stack. In Node.js 24, about 2,300 eight-byte records (under 20 KB) in one chunk are enough for `process()` to throw `RangeError: Maximum call stack size exceeded`.\n\n`ctTable` maps heartbeat records to `tls.handleHeartbeat` in every client and serv","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-10-31T22:13:31.311Z","source_updated_at":"2026-10-30T23:01:54.000Z","source_disclosed_at":"2026-10-30T23:01:54.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:55:49.621Z"}],"next_cursor":null,"snapshot_revision":"42594"}