Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-100391 – Server-Side Request Forgery (SSRF) – MediaFlow Proxy ≤ 2.4.9

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100391 is a Server-Side Request Forgery (SSRF) vulnerability in MediaFlow Proxy, an open-source media/streaming proxy application (PyPI package mediaflow-proxy, vendor mhdzumair), affecting all versions through 2.4.9. The flaw allows a remote, unauthenticated attacker to force the proxy to issue requests to internal or loopback addresses and cloud metadata endpoints, exposing the response contents to the attacker. The vulnerability is rated High severity.

Technical details

  • Root cause: the /proxy routes (including /proxy/forward and /proxy/stream) validate the destination URL supplied in the d query parameter, but the validation only checks whether the supplied host is a literal IP address in a private/internal range.
  • When a hostname is supplied instead of a literal IP (e.g., a hostname that resolves to a private, loopback, or link-local address), the guard failed to resolve it via DNS before validating, allowing the check to be bypassed entirely; the /proxy/stream endpoint reportedly had no SSRF protection at all prior to the fix.
  • Attack vector: network, no authentication or user interaction required, low attack complexity — an attacker simply crafts a request with a malicious d parameter value.
  • Impact: the proxy acts as a blind relay, fetching and returning content from internal endpoints not otherwise reachable from the internet, including cloud instance metadata services (e.g., 169.254.169.254 on AWS, Azure managed identity endpoints) and internal-network/loopback services, resulting in high-confidentiality-impact disclosure of sensitive data such as credentials or internal service responses.

Affected software

  • mediaflow-proxy (PyPI package, vendor mhdzumair) — all versions from initial release through 2.4.9.

Severity

  • CVSS v3.1 Base Score: 8.2 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
  • CVSS v4.0 Base Score: 8.8 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to a release of mediaflow-proxy that includes the corrected destination-validation guard, which resolves supplied hostnames via DNS and validates every resolved address (not just literal IP inputs) against private/internal/loopback/link-local ranges before allowing the request. The fix was merged upstream in the mediaflow_proxy/routes/proxy.py module.
  • If unable to patch immediately: restrict network egress from hosts running MediaFlow Proxy so the proxy process cannot reach internal management interfaces, loopback services, or cloud metadata endpoints (e.g., block 169.254.169.254 and RFC1918 ranges at the host/network firewall); place the proxy behind an authenticating reverse proxy or access-control layer to limit exposure to trusted clients; monitor proxy logs for requests to internal or metadata-service destinations via the d parameter.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge