Skip to main content
VulnerabilityPublished Updated

CVE-2026-100391: mhdzumair mediaflow-proxy · Server-Side Request Forgery (SSRF)

Affects mhdzumair mediaflow-proxySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2.4.10 soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.10
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 8 Nov 2026.

What to do

Upgrade mhdzumair/mediaflow-proxy to 2.4.10.

Affected software

ProductAffectedFixed in
mhdzumairmediaflow-proxyAffected
  • <=2.4.9
Fixed in–
GitHubmhdzumair/mediaflow-proxypkg:github/mhdzumair/mediaflow-proxyOther threatsAffected
  • <2.4.10
Fixed in
  • 2.4.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to the /proxy routes and implement network-level controls to prevent the proxy server from accessing sensitive internal endpoints. Validate and sanitize the 'd' query parameter to ensure only allowed destinations are reachable through the proxy.

Description

MediaFlow Proxy versions up to and including 2.4.9 contain a server-side request forgery (SSRF) vulnerability in the /proxy routes. This vulnerability arises from missing and incomplete validation of the destination URL specified in the 'd' query parameter. An unauthenticated remote attacker can exploit this flaw to make the proxy server send requests to arbitrary internal URLs, including loopback addresses and cloud metadata endpoints, potentially reading full responses from these internal resources.

References

Community reviews

Loading reviews…