BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-101907High confidence

Axios: maxRedirects: 0 is not enforced by the fetch adapter, allowing redirect-based SSRF

axios · axios

Official source article: GitHub GHSA-R4GJ-5M52-G5WH ↗. Check the applicable product and release in the original source.

7.0HighCVSS 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 110 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 28 Sep 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.41% 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

  1. Confirm that the asset runs axios axios and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 110 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

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 1 affected package state 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 releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-axiosAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian bookwormbookworm · sourcenode-axiosNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcenode-axiosVendor fix publishedDebian records a fixed source-package version for this release.1.20.0-1Debian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcenode-axiosVendor fix publishedDebian records a fixed source-package version for this release.1.20.0-1Debian Security Tracker ↗Source updated 8 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsnode-axiosUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Open-source package ranges2 source-attributed ranges

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.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmaxios>= 1.17.0, < 1.20.01.20.0GitHub advisory ↗upstream repository advisory · 30 Sep 2026
npmaxiosSEMVER: introduced 1.17.0; fixed 1.20.01.20.0OSV record ↗aggregator derived · 30 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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-101907 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityaxios: Axios: Server-Side Request Forgery via bypassed redirect restrictions in fetch adapter
9 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • grafana12.4-0:12.4.12-0.3.hum1@aarch64 as a component of Red Hat Hardened Images
  • grafana12.4-0:12.4.12-0.3.hum1@src as a component of Red Hat Hardened Images
  • grafana12.4-0:12.4.12-0.3.hum1@x86_64 as a component of Red Hat Hardened Images
  • grafana13.1-0:13.1.6-0.6.hum1@aarch64 as a component of Red Hat Hardened Images
  • grafana13.1-0:13.1.6-0.6.hum1@src as a component of Red Hat Hardened Images
  • grafana13.1-0:13.1.6-0.6.hum1@x86_64 as a component of Red Hat Hardened Images
  • grafana13.2-0:13.2.1-0.9.hum1@aarch64 as a component of Red Hat Hardened Images
  • grafana13.2-0:13.2.1-0.9.hum1@src as a component of Red Hat Hardened Images
  • grafana13.2-0:13.2.1-0.9.hum1@x86_64 as a component of Red Hat Hardened Images
Summary
A flaw was found in Axios. When configured to use the fetch adapter, the application does not enforce settings configured to disable HTTP redirects. A remote attacker controlling a redirecting server can exploit this behavior to force the application to follow redirects to internal endpoints, resulting in Server-Side Request Forgery (SSRF). This flaw can allow attackers to access internal services and expose sensitive data or trigger state-changing actions on internal systems.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
CVE-2026-101907 · CSAF 2.0 · revision 2 · interimSUSE Product Security TeamCVE-2026-101907
109 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • pgadmin4 as component of SUSE Linux Enterprise Desktop 15 SP7
  • pgadmin4-doc as component of SUSE Linux Enterprise Desktop 15 SP7
  • pgadmin4-web as component of SUSE Linux Enterprise Desktop 15 SP7
  • system-user-pgadmin as component of SUSE Linux Enterprise Desktop 15 SP7
  • pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • pgadmin4-web as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • pgadmin4-web as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation follows the redirect instead of returning the redirect response unchanged. The redirected request can access internal responses or reach state-changing internal endpoints despite redirects being disabled. This issue is fixed in version 1.20.0.
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-88384

No EUVD known-exploited evidence

Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation follows the redirect instead of returning the redirect response unchanged. The redirected request can access internal responses or reach state-changing internal endpoints despite redirects being disabled. This issue is fixed in version 1.20.0.

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
7.0 · CVSS 4.0
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 110 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

Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation follows the redirect instead of returning the redirect response unchanged. The redirected request can access internal responses or reach state-changing internal endpoints despite redirects being disabled. This issue is fixed in version 1.20.0.

What

Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation follows the redirect instead of returning the redirect response unchanged. The redirected request can access internal responses or reach state-changing internal endpoints despite redirects being disabled. This issue is fixed in version 1.20.0.

Why

The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.

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

Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation follows the redirect instead of returning the redirect response unchanged. The redirected request can access internal responses or reach state-changing internal endpoints despite redirects being disabled. This issue is fixed in version 1.20.0.

Why

The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.

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 → Unintended Proxy or Intermediary ('Confused Deputy') → 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.
CWE-441 ↗

CWE-441: Unintended Proxy or Intermediary ('Confused Deputy'). The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

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.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SIHighSubsequent-system integrity: A successful attack can cause a major loss.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-441Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-88384Official EUVD mapping

Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation follows the redirect instead of returning the redirect response unchanged. The redirected request can access internal responses or reach state-changing internal endpoints despite redirects being disabled. This issue is fixed in version 1.20.0.

Official EUVD record ↗
CSIRT Italia · Italian · disponibili-poc-per-lo-sfruttamento-di-7-vulnerabilita-in-prodotti-axiosDisponibili PoC per lo sfruttamento di 7 vulnerabilità in prodotti axios

Sono stati recentemente resi pubblici diversi Proof of Concept (PoC) relativi a 7 nuove vulnerabilità che interessano axios. Di seguito sono riportati i dettagli: CVE-2026-101909 : la vulnerabilità, di tipo " Prototype Pollution " e con CVSS 4.0 pari a 8.3, è dovuta ad una gestione non adeguata delle proprietà ereditate durante la serializzazione dei dati tramite la funzione toFormData . Un utente malintenzionato potrebbe sfruttare tale vulnerabilità per modificare la denominazione e l'interpretazione dei dati serializzati o causare fallimenti delle richieste. CVE-2026-101907 : la vulnerabilità, di tipo " Server-Side Request Forgery (SSRF) " e con CVSS 4.0 pari a 7.0, è dovuta ad una gestione non adeguata dell'opzione maxRedirects presente nell'adapter Fetch . Un utente malintenzionato potrebbe sfruttare tale vulnerabilità per eludere le restrizioni sui reindirizzamenti, consentendo all'applicazione di accedere a risorse interne o a endpoint in grado di alterare lo stato dei sistemi target. CVE-2026-101906 : la vulnerabilità, di tipo " Uncontrolled Resource Consumption " e con CVSS 4.0 pari a 8.2, è dovuta ad una gestione non adeguata degli hostname mediante espressioni regolari. Un utente malintenzionato potrebbe sfruttare tale vulnerabilità, mediante richieste con reindirizzamenti contenenti hostname opportunamente predisposti, al fine di causare un eccessivo consumo di risorse e il blocco del ciclo degli eventi di Node.js, compromettendo la disponibilità del servizio sui sistemi interessati. CVE-2026-101905 : la vulnerabilità, di tipo " Prototype Pollution ", e con CVSS 4.0 pari a 7.6, è dovuta ad una gestione non adeguata della funzione createConnection nell'adapter HTTP. Un utente malintenzionato potrebbe sfruttare tale vulnerabilità per reindirizzare le connessioni verso endpoint arbitrari sotto il proprio controllo, ottenendo l'accesso a dati sensibili, inclusi header, credenziali e contenuti delle richieste, nonché fornendo risposte manipolate all'applicazione. CVE-2026-101903 : la vulnerabilità, di tipo " Uncontrolled Resource Consumption " e con CVSS 4.0 pari a 8.2, è dovuta ad una gestione non adeguata dell'input mediante espressioni regolari. Un utente malintenzionato potrebbe sfruttare tale vulnerabilità, mediante richieste o pportunamente predisposte, al fine di causare un eccessivo consumo di risorse e il blocco del ciclo degli eventi di Node.js, compromettendo la disponibilità del servizio sui sistemi interessati. CVE-2026-101901 : la vulnerabilità, di tipo " Uncontrolled Resource Consumption " e con CVSS 4.0 pari a 8.2, è dovuta ad una gestione non adeguata degli errori nelle sessioni HTTP/2. Un utente malintenzionato potrebbe sfruttare tale vulnerabilità per provocare un errore durante l'inizializzazione o il riutilizzo di una sessione HTTP/2, al fine di generare eccezioni non gestite e causare l'arresto del processo Node.js, compromettendo la disponibilità del servizio sui sistemi interessati. CVE-2026-101898 : la vulnerabilità, di tipo " Server-Side Request Forgery (SSRF) ", e con CVSS 4.0 pari a 7.0, è dovuta ad una gestione non adeguata delle impostazioni proxy e delle policy di risoluzione DNS nelle connessioni HTTP/2. Un utente malintenzionato potrebbe sfruttare tale vulnerabilità per eludere le restrizioni di rete configurate dall'applicazione, consentendo l'accesso a risorse interne o a sistemi altrimenti non raggiungibili, compromettendo la riservatezza delle informazioni sui sistemi interessati.

Official advisory ↗
03

Patch and workaround

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.
Fix availability varies by product
Affected
axios: 1.17.0, < 1.20.0
Fixed
Action
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.
04

Evidence and provenance

Published 28 Sept 2026 · Last source change 28 Sept 2026, 18:46 UTC · CWE-441 · Unintended Proxy or Intermediary ('Confused Deputy')

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-09-29
European sourceENISA EUVD · EUVD-2026-88384
Product sourceCNA
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.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-101907 to remediation: access.redhat.com/CVE-2026-101907.
    Before
    remediation: access.redhat.com/CVE-2026-101907
    After
    remediation: access.redhat.com/CVE-2026-101907
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. 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
    After
    Fixed: grafana12.4-0:12.4.12-0.3.hum1@aarch64 as a component of Red Hat Hardened Images; grafana12.4-0:12.4.12-0.3.hum1@src as a component of Red Hat Hardened Images; grafana12.4-0:12.4.12-0.3.hum1@x86_64 as a component of Red Hat Hardened Images; grafana13.1-0:13.1.6-0.6.hum1@aarch64 as a component of Red Hat Hardened Images; grafana13.1-0:13.1.6-0.6.hum1@src as a component of Red Hat Hardened Images; grafana13.1-0:13.1.6-0.6.hum1@x86_64 as a component of Red Hat Hardened Images; grafana13.2-0:13.2.1-0.9.hum1@aarch64 as a component of Red Hat Hardened Images; grafana13.2-0:13.2.1-0.9.hum1@src as a component of Red Hat Hardened Images; grafana13.2-0:13.2.1-0.9.hum1@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  4. ENISA EUVD mappingEUVD-2026-88384 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-88384"}
    ENISA EUVD ↗
  5. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    CVE.org ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-88384↗Vendor CSAF · Red Hat Product Security↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference · GitHub GHSA-R4GJ-5M52-G5WH↗Official CVE record (CNA and ADP data)↗NVD record↗
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.
Free version - for non-commercial use only.CVE-2026-101907 · cve.blacktree.nl