CVE-2025-57814 — request-filtering-agent
CVE-2025-57814 is a Server-Side Request Forgery (SSRF) vulnerability in request-filtering-agent. A fix is available for request-filtering-agent — see the affected versions and patch details below.
request-filtering-agent SSRF Bypass via HTTPS Requests
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-57814.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
request-filtering-agentnpmDescription
request-filtering-agent 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.
Impact:
Vulnerable patterns (requests that should be blocked but are allowed):
- https://127.0.0.1:443/api
- https://127.0.0.1:8443/admin
- Any HTTPS request using direct IP address
https://127.0.0.1
This vulnerability primarily affects services using self-signed certificates on 127.0.0.1.
Not affected (correctly blocked in all versions):
- http://127.0.0.1:80/api - HTTP requests are properly blocked
- https://localhost:443/api - Domain-based requests trigger DNS lookup and are blocked
- http://localhost:80/api - Domain-based HTTP requests are blocked
- Requests to other private IPs like 192.168.x.x, 10.x.x.x, 172.16.x.x
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.
Fixed in 2.0.0
This vulnerability has been fixed in request-filtering-agent version 2.0.0. Users should upgrade to version 2.0.0 or later.
Root Cause:The HTTPS agent fails to validate direct IP addresses like https://127.0.0.1 during TLS connection setup, allowing them to bypass the security filter.
Details: https://github.com/azu/request-filtering-agent-https127-test
Thanks Luca
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | request-filtering-agent | all versions | 2.0.0npm install request-filtering-agent@2.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for request-filtering-agent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update request-filtering-agent to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-57814 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-57814 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-57814. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-57814 in your dependencies?
O3 Security finds CVE-2025-57814 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.