follow-redirects sensitiveHeaders regex escaping can expose credential headers
follow-redirects · follow-redirects
Official source article: GitHub GHSA-8R9P-F939-6H3C ↗. Check the applicable product and release in the original source.
8.2HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 19 Oct 2026
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.47% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs follow-redirects follow-redirects and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Cross-source reconciliation
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
SUSE Product Security Team: 10 affected or under-investigation product states without a fixed product state in the same current advisory
Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
Release-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
5 package states
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Distribution release
Source package
Vendor state
Fixed version
Evidence
Debian trixietrixie · source
node-follow-redirects
Affected, no fix publishedDebian currently tracks this release as open.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
2 current
CVE-2026-111755 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityfollow-redirects: follow-redirects: Information disclosure via improper regular expression escaping in sensitive header filtering
1 known affected
The vendor explicitly identifies these products as affected by this CVE.
prometheus3.5.src as a component of Red Hat Hardened Images
Summary
A flaw was found in follow-redirects. This vulnerability allows an untrusted remote server to receive sensitive credential headers due to improper handling of cross-origin redirects. When an application specifies sensitive headers containing special regular expression characters, the library fails to properly escape them when building its header filtering logic. Consequently, the protection mechanism fails to strip the sensitive headers, forwarding sensitive authentication data to third-party redirect destinations.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
The vendor explicitly identifies these products as affected by this CVE.
trento-web as component of SUSE Linux Enterprise Module for SAP Applications 15 SP4
trento-web as component of SUSE Linux Enterprise Module for SAP Applications 15 SP5
trento-web as component of SUSE Linux Enterprise Module for SAP Applications 15 SP7
trento-web as component of SUSE Linux Enterprise Server for SAP Applications 15 SP4
trento-web as component of SUSE Linux Enterprise Server for SAP Applications 15 SP5
trento-web as component of SUSE Linux Enterprise Server for SAP Applications 15 SP7
trento-web as component of SUSE Linux Enterprise Server for SAP applications 16.0
trento-web as component of SUSE Linux Enterprise Server for SAP applications 16.1
trento-web as component of openSUSE Leap 16.0
trento-web as component of openSUSE Leap 16.1
Summary
follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.
Remediation
No remediation text is recorded.
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-104536
No EUVD known-exploited evidence
ENISA has published the identifier mapping but no EUVD description has been stored yet.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product
01
What, why and how
follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.
What
follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.
Why
The product specifies a regular expression in a way that causes data to be improperly matched or compared.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
follow-redirects is a Node.js HTTP and HTTPS client wrapper that automatically follows redirects. From 1.16.0 until 1.16.1, escapeRegex leaves valid header-name metacharacters unescaped in sensitiveHeaders. When an application declares a sensitive header whose name contains ^ or | and follows a cross-origin or HTTPS-to-HTTP redirect, unescaped regular-expression metacharacters prevent the generated filter from matching the declared header name, and the credential header is forwarded to an attacker-controlled redirect target. This issue is fixed in version 1.16.1.
Why
The product specifies a regular expression in a way that causes data to be improperly matched or compared.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
Likely attack path
a network path → Incorrect Regular Expression → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
Official EUVD record ↗BSI · German · WID-SEC-2026-4634Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye und Jira): Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.
Official advisory ↗NCSC-NL · Dutch · NCSC-2026-0496Kwetsbaarheden verholpen in Atlassian producten
A vulnerability in follow-redirects versions 1.16.0 to 1.16.1 causes sensitive credential headers containing regex metacharacters to be leaked to untrusted redirect targets due to improper escaping in the sensitiveHeaders filter.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
Security Bulletin - November 17 2026 | Atlassian Support | Atlassian Documentation →Original publisher ↗Searchable text snapshot · Captured 19 Nov 2026Unable to load
Security Bulletin - November 17 2026
Security Advisories & Bulletins
November 2022: Atlassian Security Advisories Overview
Archived Security Advisories
Security Advisories for Apps
July 2022: Atlassian Security Advisories Overview
August 2022: Atlassian Security Advisories Overview
January 2023: Sec
04
Evidence and provenance
Published 19 Oct 2026 · Last source change 19 Oct 2026, 18:00 UTC · CWE-185 · Incorrect Regular Expression
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-10-21
European sourceENISA EUVD · EUVD-2026-104536
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
grafana12.4.src as a component of Red Hat Hardened Images; grafana13.1.src as a component of Red Hat Hardened Images; grafana13.2.src as a component of Red Hat Hardened Images; prometheus3.13.src as a component of Red Hat Hardened Images; prometheus3.5.src as a component of Red Hat Hardened Images
After
prometheus3.5.src as a component of Red Hat Hardened Images · Fixed: grafana12.4-0:12.4.13-0.3.hum1@aarch64 as a component of Red Hat Hardened Images; grafana12.4-0:12.4.13-0.3.hum1@src as a component of Red Hat Hardened Images; grafana12.4-0:12.4.13-0.3.hum1@x86_64 as a component of Red Hat Hardened Images; grafana13.1-0:13.1.8-0.4.hum1@aarch64 as a component of Red Hat Hardened Images; grafana13.1-0:13.1.8-0.4.hum1@s390x as a component of Red Hat Hardened Images; grafana13.1-0:13.1.8-0.4.hum1@src as a component of Red Hat Hardened Images; grafana13.1-0:13.1.8-0.4.hum1@x86_64 as a component of Red Hat Hardened Images; grafana13.2-0:13.2.4-0.3.hum1@aarch64 as a component of Red Hat Hardened Images; grafana13.2-0:13.2.4-0.3.hum1@s390x as a component of Red Hat Hardened Images; grafana13.2-0:13.2.4-0.3.hum1@src as a component of Red Hat Hardened Images; grafana13.2-0:13.2.4-0.3.hum1@x86_64 as a component of Red Hat Hardened Images
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.