{"id":"CVE-2026-116689","aliases":["CLSA-2026-1793790104","CLSA-2026-1793801934","CLSA-2026-1793808705","CLSA-2026-1793813951","CLSA-2026-1793828720","CLSA-2026-1793874839","DEBIAN-CVE-2026-116689","EUVD-2026-111363","GHSA-mrwp-f3q8-3g9p","ROOT-APP-NPM-CVE-2026-116689","UBUNTU-CVE-2026-116689","openSUSE-SU-2026:12424-1"],"status":"published","title":"follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects","description":"follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.","severity":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00266,"percentile":0.18941,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-201"],"published":"2026-10-27T19:38:46Z","modified":"2026-11-06T17:27:19Z","fixes":[{"ecosystem":"npm","package":"follow-redirects","fixed_in":["1.16.2"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:npm","package":"follow-redirects","fixed_in":["1.15.11-tuxcare.5","1.15.9-tuxcare.2","1.15.6-tuxcare.3","1.15.5-tuxcare.3","1.15.3-tuxcare.2","1.15.2-tuxcare.4"],"sources":["osv"]},{"ecosystem":"Root:npm","package":"follow-redirects","fixed_in":["1.16.0-aikido.2","1.16.1-aikido.1"],"sources":["osv"]},{"ecosystem":"Root:npm","package":"@rootio/follow-redirects","fixed_in":["1.16.0-root.io.2","1.16.1-root.io.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.16.0"},{"last_affected":"1.16.1"},{"fixed":"1.16.2"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.15.11-tuxcare.0"},{"fixed":"1.15.11-tuxcare.5"}]}],"versions":["1.15.11","1.15.11-tuxcare.1","1.15.11-tuxcare.2","1.15.11-tuxcare.3","1.15.11-tuxcare.4"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.15.9-tuxcare.0"},{"fixed":"1.15.9-tuxcare.2"}]}],"versions":["1.15.9","1.15.9-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.15.6-tuxcare.0"},{"fixed":"1.15.6-tuxcare.3"}]}],"versions":["1.15.6","1.15.6-tuxcare.1","1.15.6-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.15.5-tuxcare.0"},{"fixed":"1.15.5-tuxcare.3"}]}],"versions":["1.15.5","1.15.5-tuxcare.1","1.15.5-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.15.3-tuxcare.0"},{"fixed":"1.15.3-tuxcare.2"}]}],"versions":["1.15.3","1.15.3-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.15.2-tuxcare.0"},{"fixed":"1.15.2-tuxcare.4"}]}],"versions":["1.15.2","1.15.2-tuxcare.1","1.15.2-tuxcare.2","1.15.2-tuxcare.3"]},{"source":"osv","ecosystem":"Debian:12","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.15.11+~1.14.4-1","1.15.11+~1.14.4-2","1.15.2+~1.14.1-1","1.15.3+~1.14.2-1","1.15.6+~1.14.4-1","1.15.6+~1.14.4-2","1.15.9+~1.14.4-1","1.16.0+~1.14.4-1","1.16.0+~1.14.4-2","1.16.1+~1.14.4-1"]},{"source":"osv","ecosystem":"Debian:13","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.15.11+~1.14.4-1","1.15.11+~1.14.4-2","1.15.9+~1.14.4-1","1.16.0+~1.14.4-1","1.16.0+~1.14.4-2","1.16.1+~1.14.4-1"]},{"source":"osv","ecosystem":"Debian:14","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.15.11+~1.14.4-1","1.15.11+~1.14.4-2","1.15.9+~1.14.4-1","1.16.0+~1.14.4-1","1.16.0+~1.14.4-2","1.16.1+~1.14.4-1"]},{"source":"osv","ecosystem":"npm","package":"follow-redirects","ranges":[{"type":"SEMVER","events":[{"introduced":"1.16.0"},{"fixed":"1.16.2"}]}]},{"source":"osv","ecosystem":"Root:npm","package":"follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.0-aikido.2"},{"fixed":"1.16.1-aikido.1"}]}]},{"source":"osv","ecosystem":"Root:npm","package":"@rootio/follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.0-root.io.2"},{"fixed":"1.16.1-root.io.1"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.4-1","1.2.4-1ubuntu0.18.04.1~esm1","1.2.4-1ubuntu0.18.04.1~esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.4-1","1.2.4-1ubuntu0.20.04.1~esm1","1.2.4-1ubuntu0.20.04.1~esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.13.1-1","1.14.5-1","1.14.7+~1.13.1-1","1.14.8+~1.14.0-1","1.14.9+~1.14.1-1","1.14.9+~1.14.1-1ubuntu0.1~esm1","1.14.9+~1.14.1-1ubuntu0.1~esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.15.2+~1.14.1-1","1.15.3+~1.14.2-1","1.15.6+~1.14.4-1","1.15.6+~1.14.4-1ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.15.11+~1.14.4-1build1","1.16.0+~1.14.4-2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:26.04:LTS","package":"node-follow-redirects","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.15.9+~1.14.4-1","1.15.11+~1.14.4-1build1","1.15.11+~1.14.4-1ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"agama-web-ui","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"25+475.275dd4727-56.1"}]}],"bundled":11}],"products":[{"vendor":"follow-redirects","product":"follow-redirects"}],"references":[{"url":"https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-mrwp-f3q8-3g9p","tags":["x_refsource_CONFIRM","exploit","advisory","web","report"]},{"url":"https://github.com/follow-redirects/follow-redirects/commit/b0a7751e9cd64cd8eeb6ec67d2f206a9cc88d3f8","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://github.com/follow-redirects/follow-redirects/releases/tag/v1.16.2","tags":["x_refsource_MISC","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116689","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-mrwp-f3q8-3g9p"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/116xxx/CVE-2026-116689.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-116689","tags":["advisory"]},{"url":"https://github.com/follow-redirects/follow-redirects","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2026-116689","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-116689","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-102277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-110725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-111181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-111755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-111756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-115754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-115897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-116689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-75899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86472","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-116689","title":"follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects","description":"follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.","status":"published","published":"2026-10-27T19:38:46.034Z","modified":"2026-10-30T18:47:54.616Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-201"],"updated_at":"2026-11-02T14:20:03.4818Z"}],"euvd":[{"id":"EUVD-2026-111363","description":"follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.","status":"published","published":"2026-10-27T19:38:46Z","modified":"2026-10-30T18:47:54Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T16:59:02.630385Z"}],"ghsa":[{"id":"GHSA-mrwp-f3q8-3g9p","title":"follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects","description":"### Summary\n\nfollow-redirects 1.16.0 and 1.16.1 validate the documented sensitiveHeaders option with instanceof Array. An array created in another JavaScript realm is silently replaced with an empty list, so a caller-declared custom credential header can be forwarded to an attacker-controlled cross-origin redirect destination.\n\n### Details\n\nAffected versions\n\nThe sensitiveHeaders option was introduced in 1.16.0. Published 1.16.0 and 1.16.1 both reproduced, giving a tested affected range of 1.16.0 through 1.16.1. The source checkout was pinned at revision 46301256333c90b7faac7aa126effe72ec16d16e; the exact npm 1.16.1 artifact reproduced independently.\n\nRoot cause\n\nindex.js resets options.sensitiveHeaders when its local isArray() helper returns false. That helper uses value instanceof Array, which depends on realm identity. The same file already uses Array.isArray(options.headers), which correctly recognizes arrays across realms.\n\nSuggested remediation\n\nUse Array.isArray(value) for sensitiveHeaders, then validate and normalize each member as a header-name string. Add same-realm and node:vm cross-realm tests for cross-origin redirects, including the array-form headers representation. Verify that custom sensitive names are removed while unrelated headers remain unchanged.\n\nDuplicate review\n\nThe public advisory history contains other sensitive-header findings, including array-form headers and regular-expression handling, but focused repository searches found no report describing cross-realm validation as of 2026-10-25. A private or differently worded report may already exist.\n\n### Proof of concept\n\nStart two loopback HTTP servers. The first returns a 302 redirect to the second. Send X-API-Key and list that name in sensitiveHeaders, then compare a normal array with a genuine cross-realm array created by:\n\n```js\nconst vm = require('node:vm');\nconst sensitiveHeaders = vm.runInNewContext(`['X-API-Key']`);\n```\n\nObserved against both source and the exact npm 1.16.1 package:\n\n- Same-realm ['X-API-Key']: the redirect target did not receive the key.\n- Cross-realm ['X-API-Key']: Array.isArray(value) was true, value instanceof Array was false, and the redirect target received X-API-Key.\n- An unrelated X-Harmless header remained present in both cases.\n\nThe complete 3.5 KB loopback-only harness and raw JSON output are available privately.\n\n### Impact\n\ncustom credential disclosure. Exploitation requires a direct caller or wrapper that preserves a cross-realm sensitiveHeaders array, a custom credential listed in that option, and an attacker-controlled or compromised endpoint that returns a cross-origin redirect. The directly demonstrated result is disclosure of the custom header value, potentially exposing an API key or service token until revocation.\n\nBuilt-in Authorization, Proxy-Authorization, and Cookie protections remained effective. Exact Axios 1.20.0 with follow-redirects 1.16.1 did not reproduce because Axios normalized the array; this report does not claim that Axios is affected. No third-party service was tested.","status":"published","published":"2026-10-30T22:59:33Z","modified":"2026-10-30T22:59:34Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-201"],"updated_at":"2026-11-02T14:41:41.028239Z"}],"nvd":[{"id":"CVE-2026-116689","description":"follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.","status":"published","published":"2026-10-27T20:17:14.177Z","modified":"2026-10-30T19:18:14.49Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-201"],"updated_at":"2026-11-02T14:13:04.037468Z"}],"osv":[{"id":"CVE-2026-116689","title":"follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects","description":"follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.","status":"published","published":"2026-10-27T19:38:46.034Z","modified":"2026-11-06T17:27:19.166033339Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-201"],"updated_at":"2026-11-06T18:03:33.161875Z"},{"id":"DEBIAN-CVE-2026-116689","description":"follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.","status":"published","published":"2026-10-27T20:17:14.177Z","modified":"2026-10-31T09:47:33.922797767Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:50.923612Z"},{"id":"GHSA-mrwp-f3q8-3g9p","title":"follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects","description":"### Summary\n\nfollow-redirects 1.16.0 and 1.16.1 validate the documented sensitiveHeaders option with instanceof Array. An array created in another JavaScript realm is silently replaced with an empty list, so a caller-declared custom credential header can be forwarded to an attacker-controlled cross-origin redirect destination.\n\n### Details\n\nAffected versions\n\nThe sensitiveHeaders option was introduced in 1.16.0. Published 1.16.0 and 1.16.1 both reproduced, giving a tested affected range of 1.16.0 through 1.16.1. The source checkout was pinned at revision 46301256333c90b7faac7aa126effe72ec16d16e; the exact npm 1.16.1 artifact reproduced independently.\n\nRoot cause\n\nindex.js resets options.sensitiveHeaders when its local isArray() helper returns false. That helper uses value instanceof Array, which depends on realm identity. The same file already uses Array.isArray(options.headers), which correctly recognizes arrays across realms.\n\nSuggested remediation\n\nUse Array.isArray(value) for sensitiveHeaders, then validate and normalize each member as a header-name string. Add same-realm and node:vm cross-realm tests for cross-origin redirects, including the array-form headers representation. Verify that custom sensitive names are removed while unrelated headers remain unchanged.\n\nDuplicate review\n\nThe public advisory history contains other sensitive-header findings, including array-form headers and regular-expression handling, but focused repository searches found no report describing cross-realm validation as of 2026-10-25. A private or differently worded report may already exist.\n\n### Proof of concept\n\nStart two loopback HTTP servers. The first returns a 302 redirect to the second. Send X-API-Key and list that name in sensitiveHeaders, then compare a normal array with a genuine cross-realm array created by:\n\n```js\nconst vm = require('node:vm');\nconst sensitiveHeaders = vm.runInNewContext(`['X-API-Key']`);\n```\n\nObserved against both source and the exact npm 1.16.1 package:\n\n- Same-realm ['X-API-Key']: the redirect target did not receive the key.\n- Cross-realm ['X-API-Key']: Array.isArray(value) was true, value instanceof Array was false, and the redirect target received X-API-Key.\n- An unrelated X-Harmless header remained present in both cases.\n\nThe complete 3.5 KB loopback-only harness and raw JSON output are available privately.\n\n### Impact\n\ncustom credential disclosure. Exploitation requires a direct caller or wrapper that preserves a cross-realm sensitiveHeaders array, a custom credential listed in that option, and an attacker-controlled or compromised endpoint that returns a cross-origin redirect. The directly demonstrated result is disclosure of the custom header value, potentially exposing an API key or service token until revocation.\n\nBuilt-in Authorization, Proxy-Authorization, and Cookie protections remained effective. Exact Axios 1.20.0 with follow-redirects 1.16.1 did not reproduce because Axios normalized the array; this report does not claim that Axios is affected. No third-party service was tested.","status":"published","published":"2026-10-30T22:59:33Z","modified":"2026-10-30T23:15:06.31525175Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium"},{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-201"],"updated_at":"2026-11-02T15:46:52.170928Z"},{"id":"UBUNTU-CVE-2026-116689","description":"follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.2, the documented sensitiveHeaders option is checked with value instanceof Array, so an array created in another JavaScript realm is replaced with an empty list even though Array.isArray recognizes it. When a request then follows an attacker-controlled cross-origin redirect, a custom credential header named in that discarded list can be forwarded to the redirect destination. This issue is fixed in version 1.16.2.","status":"published","published":"2026-10-27T20:17:00Z","modified":"2026-10-28T20:17:45.942941991Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T16:56:00.081948Z"},{"id":"CLSA-2026-1793790104","title":"TuxCare security update for follow-redirects (1 CVE)","description":"TuxCare rebuilt follow-redirects to address 1 CVE. Fixed in 1.15.11-tuxcare.5.","status":"published","published":"2026-11-04T12:01:44Z","modified":"2026-11-04T14:45:04.307147237Z","updated_at":"2026-11-04T15:03:54.132276Z"},{"id":"CLSA-2026-1793801934","title":"TuxCare security update for follow-redirects (1 CVE)","description":"TuxCare rebuilt follow-redirects to address 1 CVE. Fixed in 1.15.9-tuxcare.2.","status":"published","published":"2026-11-04T15:18:55Z","modified":"2026-11-04T19:00:35.340701715Z","updated_at":"2026-11-04T19:15:03.6858Z"},{"id":"CLSA-2026-1793808705","title":"TuxCare security update for follow-redirects (1 CVE)","description":"TuxCare rebuilt follow-redirects to address 1 CVE. Fixed in 1.15.6-tuxcare.3.","status":"published","published":"2026-11-04T17:11:46Z","modified":"2026-11-04T19:00:37.191946059Z","updated_at":"2026-11-04T19:15:03.6858Z"},{"id":"CLSA-2026-1793813951","title":"TuxCare security update for follow-redirects (1 CVE)","description":"TuxCare rebuilt follow-redirects to address 1 CVE. Fixed in 1.15.5-tuxcare.3.","status":"published","published":"2026-11-04T18:39:12Z","modified":"2026-11-05T01:00:03.609385048Z","updated_at":"2026-11-05T01:12:05.565404Z"},{"id":"CLSA-2026-1793828720","title":"TuxCare security update for follow-redirects (1 CVE)","description":"TuxCare rebuilt follow-redirects to address 1 CVE. Fixed in 1.15.3-tuxcare.2.","status":"published","published":"2026-11-04T22:45:21Z","modified":"2026-11-05T01:00:02.599299925Z","updated_at":"2026-11-05T01:12:05.565404Z"},{"id":"CLSA-2026-1793874839","title":"TuxCare security update for follow-redirects (1 CVE)","description":"TuxCare rebuilt follow-redirects to address 1 CVE. Fixed in 1.15.2-tuxcare.4.","status":"published","published":"2026-11-05T11:34:00Z","modified":"2026-11-05T13:15:18.094875694Z","updated_at":"2026-11-05T13:30:00.949926Z"},{"id":"openSUSE-SU-2026:12424-1","title":"agama-web-ui-25+475.275dd4727-56.1 on GA media","description":"These are all security issues fixed in the agama-web-ui-25+475.275dd4727-56.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-11-05T00:00:00Z","modified":"2026-11-06T17:23:11.345171291Z","updated_at":"2026-11-06T18:05:03.243497Z"},{"id":"ROOT-APP-NPM-CVE-2026-116689","title":"CVE-2026-116689 in follow-redirects - Patched by Root","description":"Root has patched CVE-2026-116689 in the follow-redirects package for Root:npm. Multiple fixed versions available.","status":"published","published":"2026-11-03T09:09:15Z","modified":"2026-11-03T10:15:02.836269226Z","updated_at":"2026-11-06T14:57:18.209369Z"}]}}