Skip to main content
CVE-2025-57814VulnerabilityPublished

CVE-2025-57814: azu request-filtering-agent · Server-Side Request Forgery (SSRF)

Affects azu request-filtering-agentSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.0.0 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade azu request-filtering-agent to 2.0.0.

Affected software

ProductAffectedFixed in
azu request-filtering-agentAffected
  • <2.0.0
Fixed in
  • 2.0.0

AI-suggested

European organizations should immediately audit their use of the azu request-filtering-agent library and identify any deployments running versions earlier than 2.0.0. The primary mitigation is to upgrade to version 2.0.0 or later, which contains the fix for HTTPS localhost request filtering. Additionally, organizations should implement strict input validation and sanitization on any user-controlled URLs to prevent injection of malicious requests. Network segmentation and zero-trust principles should be enforced to reduce reliance on network-level protections alone. Internal services should require strong authentication and authorization controls rather than relying solely on IP-based restrictions. Monitoring and logging of outbound HTTP(S) requests from applications can help detect anomalous SSRF attempts. Finally, penetration testing and code reviews focusing on SSRF vectors should be conducted to identify and remediate similar vulnerabilities.

Description

request-filtering-agent is an http(s).Agent implementation that blocks requests to Private/Reserved IP addresses. Versions 1.x.x and earlier contain a vulnerability where HTTPS requests to 127.0.0.1 bypass IP address filtering, while HTTP requests are correctly blocked. This allows attackers to potentially access internal HTTPS services running on localhost, bypassing the library's SSRF protection. The vulnerability is particularly dangerous when the application accepts user-controlled URLs and internal services are only protected by network-level restrictions. This vulnerability has been fixed in request-filtering-agent version 2.0.0. Users should upgrade to version 2.0.0 or later.

References

Community reviews

Loading reviews…