{"items":[{"id":"NVI-00009171","kind":"vulnerability","title":"Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie","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-6wvx-3r32-xmcg","CVE-2026-118777"],"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-071e9630d704f9c9b2090c22d8f01e01"],"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-46d5cb7f84f597dc4af627b9ae6659eb"],"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:39.000Z","value":"4.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-dedead8704789098c62205e3e9e23074"},{"kind":"CVSS","as_of":"2026-11-04T16:49:51.240Z","value":"4.8 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-213a1b0c1c61f6ae18fa1596b84e4520"},{"kind":"CVSS","as_of":"2026-11-04T16:49:51.240Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-213a1b0c1c61f6ae18fa1596b84e4520"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.255%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.17184. Missing scores are unknown.","source_id":"sr-071e9630d704f9c9b2090c22d8f01e01"}],"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-dedead8704789098c62205e3e9e23074","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-46d5cb7f84f597dc4af627b9ae6659eb","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:34.928Z"},{"id":"sr-213a1b0c1c61f6ae18fa1596b84e4520","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118777","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-118777","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-07T07:00:25.983Z"},{"id":"sr-071e9630d704f9c9b2090c22d8f01e01","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-118777","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.778Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-dedead8704789098c62205e3e9e23074"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-46d5cb7f84f597dc4af627b9ae6659eb"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-07T18:43:12.073Z","source_updated_at":"2026-10-30T23:02:39.000Z","source_disclosed_at":"2026-10-30T23:02:35.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-00009171","kind":"vulnerability","title":"Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie","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-6wvx-3r32-xmcg","CVE-2026-118777"],"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-071e9630d704f9c9b2090c22d8f01e01"],"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-46d5cb7f84f597dc4af627b9ae6659eb"],"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:39.000Z","value":"4.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-dedead8704789098c62205e3e9e23074"},{"kind":"CVSS","as_of":"2026-10-30T17:17:16.110Z","value":"4.8 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0606369f7eeddc4ae8e216a04a93fb6c"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.255%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.17184. Missing scores are unknown.","source_id":"sr-071e9630d704f9c9b2090c22d8f01e01"}],"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-dedead8704789098c62205e3e9e23074","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-46d5cb7f84f597dc4af627b9ae6659eb","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:34.928Z"},{"id":"sr-0606369f7eeddc4ae8e216a04a93fb6c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118777","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-118777","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:16.598Z"},{"id":"sr-071e9630d704f9c9b2090c22d8f01e01","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-118777","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.778Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-dedead8704789098c62205e3e9e23074"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-46d5cb7f84f597dc4af627b9ae6659eb"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-04T10:04:41.554Z","source_updated_at":"2026-10-30T23:02:39.000Z","source_disclosed_at":"2026-10-30T23:02:35.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-00009171","kind":"vulnerability","title":"Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie","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-6wvx-3r32-xmcg","CVE-2026-118777"],"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-88f32aaf40179392e82752ce2b7254d9"],"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-46d5cb7f84f597dc4af627b9ae6659eb"],"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:39.000Z","value":"4.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-dedead8704789098c62205e3e9e23074"},{"kind":"CVSS","as_of":"2026-10-30T17:17:16.110Z","value":"4.8 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0606369f7eeddc4ae8e216a04a93fb6c"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.255%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.17162. Missing scores are unknown.","source_id":"sr-88f32aaf40179392e82752ce2b7254d9"}],"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-dedead8704789098c62205e3e9e23074","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-46d5cb7f84f597dc4af627b9ae6659eb","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:34.928Z"},{"id":"sr-0606369f7eeddc4ae8e216a04a93fb6c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118777","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-118777","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:16.598Z"},{"id":"sr-88f32aaf40179392e82752ce2b7254d9","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-118777","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.375Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-dedead8704789098c62205e3e9e23074"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-46d5cb7f84f597dc4af627b9ae6659eb"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-03T10:03:31.367Z","source_updated_at":"2026-10-30T23:02:39.000Z","source_disclosed_at":"2026-10-30T23:02:35.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-00009171","kind":"vulnerability","title":"Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6wvx-3r32-xmcg","CVE-2026-118777"],"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-88f32aaf40179392e82752ce2b7254d9"],"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-46d5cb7f84f597dc4af627b9ae6659eb"],"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:39.000Z","value":"4.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-dedead8704789098c62205e3e9e23074"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.255%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.17162. Missing scores are unknown.","source_id":"sr-88f32aaf40179392e82752ce2b7254d9"}],"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-dedead8704789098c62205e3e9e23074","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-46d5cb7f84f597dc4af627b9ae6659eb","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:34.928Z"},{"id":"sr-88f32aaf40179392e82752ce2b7254d9","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-118777","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.375Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-dedead8704789098c62205e3e9e23074"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-46d5cb7f84f597dc4af627b9ae6659eb"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-03T02:33:09.123Z","source_updated_at":"2026-10-30T23:02:39.000Z","source_disclosed_at":"2026-10-30T23:02:35.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-00009171","kind":"vulnerability","title":"Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6wvx-3r32-xmcg","CVE-2026-118777"],"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-dedead8704789098c62205e3e9e23074"],"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-46d5cb7f84f597dc4af627b9ae6659eb"],"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:39.000Z","value":"4.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-dedead8704789098c62205e3e9e23074"}],"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-dedead8704789098c62205e3e9e23074","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-46d5cb7f84f597dc4af627b9ae6659eb","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-01T00:58:34.928Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-dedead8704789098c62205e3e9e23074"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["<= 1.4.0"]},{"certainty":"source_listed","source_ids":["sr-46d5cb7f84f597dc4af627b9ae6659eb"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["SEMVER: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-01T01:03:56.578Z","source_updated_at":"2026-10-30T23:02:39.000Z","source_disclosed_at":"2026-10-30T23:02:35.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-00009171","kind":"vulnerability","title":"Forge: Prototype Pollution in forge.http cookie handling via a malicious Set-Cookie","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6wvx-3r32-xmcg","CVE-2026-118777"],"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-dedead8704789098c62205e3e9e23074"],"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:39.000Z","value":"4.8 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-dedead8704789098c62205e3e9e23074"}],"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-dedead8704789098c62205e3e9e23074","url":"https://github.com/advisories/GHSA-6wvx-3r32-xmcg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6wvx-3r32-xmcg","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-dedead8704789098c62205e3e9e23074"],"technology":"node-forge","known_exclusions":[],"conditions_summary":"### Summary\nThe `forge.http` client stored cookies from `Set-Cookie` response headers in a plain object keyed by cookie name and path. A malicious server could use the cookie name `__proto__` to add properties to `Object.prototype`, use inherited names such as `constructor` to add properties to `Object`, and send an empty cookie value to delete `Object.prototype` properties. Fixed in node-forge 1.4.1.\n\n### Details\n`client.setCookie()` in `lib/http.js` stored a cookie with `client.cookies[cookie.name][cookie.path] = cookie`, creating `client.cookies[cookie.name]` only when `!(cookie.name in client.cookies)`. Both values come from the server's `Set-Cookie` header via `response.getCookies()`. Because `in` also sees inherited properties:\n\n- a cookie named `__proto__` skipped the initialization, `client.cookies['__proto__']` returned `Object.prototype`, and the cookie path was written as a new `Object.prototype` property, visible on every object;\n- a cookie named `constructor` wrote onto the global `Object` function the same way;\n- a cookie with an empty value calls `client.removeCookie(name, path)`, which used the same `in` checks and then `delete client.cookies[name][path]`, so `Set-C","public_affected_ranges":["<= 1.4.0"]}],"null_published_at":"2026-10-31T22:13:31.288Z","source_updated_at":"2026-10-30T23:02:39.000Z","source_disclosed_at":"2026-10-30T23:02:35.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"}