{"items":[{"id":"NVI-00008878","kind":"vulnerability","title":"Forge: AES-GCM authentication bypass via unvalidated tagLength option","revision":6,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-5cwg-6vw7-rj6p","CVE-2026-119186"],"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-09c99f902b1d3149b62b41a89e7b9dab"],"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-2b2190c05044d201fbc84f833143a8fd"],"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:02:10.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1600419d0564575d4c58292e8c883b5b"},{"kind":"CVSS","as_of":"2026-10-30T17:18:03.880Z","value":"5.9 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-16ea721086ebb9dfe7c890012f81a1ef"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.206%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.10763. Missing scores are unknown.","source_id":"sr-09c99f902b1d3149b62b41a89e7b9dab"}],"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-1600419d0564575d4c58292e8c883b5b","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-2b2190c05044d201fbc84f833143a8fd","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:42.149Z"},{"id":"sr-16ea721086ebb9dfe7c890012f81a1ef","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-119186","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-119186","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:16.598Z"},{"id":"sr-09c99f902b1d3149b62b41a89e7b9dab","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-119186","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.317Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1600419d0564575d4c58292e8c883b5b"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-2b2190c05044d201fbc84f833143a8fd"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-06T07:24:11.295Z","source_updated_at":"2026-10-30T23:02:10.000Z","source_disclosed_at":"2026-10-30T23:02:09.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-00008878","kind":"vulnerability","title":"Forge: AES-GCM authentication bypass via unvalidated tagLength option","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-5cwg-6vw7-rj6p","CVE-2026-119186"],"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-16ec5c1f6f1a98c7e1497302e64f359c"],"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-2b2190c05044d201fbc84f833143a8fd"],"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:02:10.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1600419d0564575d4c58292e8c883b5b"},{"kind":"CVSS","as_of":"2026-10-30T17:18:03.880Z","value":"5.9 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-16ea721086ebb9dfe7c890012f81a1ef"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.206%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.1069. Missing scores are unknown.","source_id":"sr-16ec5c1f6f1a98c7e1497302e64f359c"}],"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-1600419d0564575d4c58292e8c883b5b","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-2b2190c05044d201fbc84f833143a8fd","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:42.149Z"},{"id":"sr-16ea721086ebb9dfe7c890012f81a1ef","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-119186","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-119186","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:16.598Z"},{"id":"sr-16ec5c1f6f1a98c7e1497302e64f359c","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-119186","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.268Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1600419d0564575d4c58292e8c883b5b"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-2b2190c05044d201fbc84f833143a8fd"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-03T17:49:18.503Z","source_updated_at":"2026-10-30T23:02:10.000Z","source_disclosed_at":"2026-10-30T23:02:09.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-00008878","kind":"vulnerability","title":"Forge: AES-GCM authentication bypass via unvalidated tagLength option","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-5cwg-6vw7-rj6p","CVE-2026-119186"],"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-569f7c6943eeba6a87549d1f01601357"],"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-2b2190c05044d201fbc84f833143a8fd"],"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:02:10.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1600419d0564575d4c58292e8c883b5b"},{"kind":"CVSS","as_of":"2026-10-30T17:18:03.880Z","value":"5.9 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-16ea721086ebb9dfe7c890012f81a1ef"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.206%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.10693. Missing scores are unknown.","source_id":"sr-569f7c6943eeba6a87549d1f01601357"}],"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-1600419d0564575d4c58292e8c883b5b","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-2b2190c05044d201fbc84f833143a8fd","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:42.149Z"},{"id":"sr-16ea721086ebb9dfe7c890012f81a1ef","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-119186","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-119186","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:16.598Z"},{"id":"sr-569f7c6943eeba6a87549d1f01601357","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-119186","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.375Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1600419d0564575d4c58292e8c883b5b"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-2b2190c05044d201fbc84f833143a8fd"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-03T10:03:31.373Z","source_updated_at":"2026-10-30T23:02:10.000Z","source_disclosed_at":"2026-10-30T23:02:09.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"},{"id":"NVI-00008878","kind":"vulnerability","title":"Forge: AES-GCM authentication bypass via unvalidated tagLength option","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5cwg-6vw7-rj6p","CVE-2026-119186"],"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-569f7c6943eeba6a87549d1f01601357"],"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-2b2190c05044d201fbc84f833143a8fd"],"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:02:10.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1600419d0564575d4c58292e8c883b5b"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.206%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.10693. Missing scores are unknown.","source_id":"sr-569f7c6943eeba6a87549d1f01601357"}],"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-1600419d0564575d4c58292e8c883b5b","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-2b2190c05044d201fbc84f833143a8fd","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:42.149Z"},{"id":"sr-569f7c6943eeba6a87549d1f01601357","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-119186","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.375Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1600419d0564575d4c58292e8c883b5b"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-2b2190c05044d201fbc84f833143a8fd"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-01T01:45:38.500Z","source_updated_at":"2026-10-30T23:02:10.000Z","source_disclosed_at":"2026-10-30T23:02:09.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-00008878","kind":"vulnerability","title":"Forge: AES-GCM authentication bypass via unvalidated tagLength option","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5cwg-6vw7-rj6p","CVE-2026-119186"],"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-1600419d0564575d4c58292e8c883b5b"],"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-2b2190c05044d201fbc84f833143a8fd"],"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:02:10.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1600419d0564575d4c58292e8c883b5b"}],"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-1600419d0564575d4c58292e8c883b5b","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-2b2190c05044d201fbc84f833143a8fd","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:42.149Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1600419d0564575d4c58292e8c883b5b"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-2b2190c05044d201fbc84f833143a8fd"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-01T01:03:56.577Z","source_updated_at":"2026-10-30T23:02:10.000Z","source_disclosed_at":"2026-10-30T23:02:09.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"},{"id":"NVI-00008878","kind":"vulnerability","title":"Forge: AES-GCM authentication bypass via unvalidated tagLength option","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5cwg-6vw7-rj6p","CVE-2026-119186"],"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-1600419d0564575d4c58292e8c883b5b"],"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}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:02:10.000Z","value":"5.9 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1600419d0564575d4c58292e8c883b5b"}],"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-1600419d0564575d4c58292e8c883b5b","url":"https://github.com/advisories/GHSA-5cwg-6vw7-rj6p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5cwg-6vw7-rj6p","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1600419d0564575d4c58292e8c883b5b"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\n\nThe AES-GCM mode in forge.cipher does not validate the tagLength option passed to start(). With a tagLength of 0 or a value that converts to 0 (such as null, false, '' or '0'), the authentication tag is empty, and decipher.finish() returns true for any ciphertext and additional data when the supplied tag is empty or missing. Fixed in node-forge 1.4.1.\n\n### Details\n\n`modes.gcm.prototype.start()` in `lib/cipherModes.js` stored the `tagLength` option without validation, and `lib/cipher.js` documented it as accepting \"0-128\". After processing the data, `afterFinish()` truncates the 16-byte tag with `truncate(16 % (tagLength / 8))`. For a `tagLength` that converts to 0, this is `16 % 0 = NaN`, and truncating by `NaN` empties the tag. On decryption, the start-time check that the supplied `tag` has `tagLength / 8` bytes passes for an empty tag, and the final tag comparison compares two empty strings, so `decipher.finish()` returns `true` for any ciphertext and additional data.\n\nNIST SP 800-38D section 5.2.1.2 allows only tag lengths of 128, 120, 112, 104 and 96 bits, plus 64 and 32 bits for certain applications.\n\nThe fix validates `tagLength` in `start()`, for both encryption","public_affected_ranges":["<= 1.4.0"]}],"null_published_at":"2026-10-31T22:13:27.120Z","source_updated_at":"2026-10-30T23:02:10.000Z","source_disclosed_at":"2026-10-30T23:02:09.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:55:49.621Z"}],"next_cursor":null,"snapshot_revision":"42594"}