Skip to content
Web

CVE-2025-61506

9.8
Critical
EPSS 0.66%

Critical unauthenticated file upload on /upload.

exploited
Unvetted proof-of-concept code on GitHub no exploitation in the wild known; not in CISA KEV
fix
No fixed release stated by the publisher
likelihood
EPSS 0.66%top 48% of scored CVEs
Published 3 Feb 2026Analysed here 5 Feb 2026CVSS scored by CISA
common questions

Is CVE-2025-61506 being exploited?

Not confirmed. CVE-2025-61506 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.66% probability of exploitation in the next 30 days.

How severe is CVE-2025-61506?

CVE-2025-61506 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-61506?

Not known from our data. No patch reference has been recorded for CVE-2025-61506, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-61506 affect?

CVE-2025-61506 affects MediaCrush. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-61506?

Patch when available; enforce upload validation and auth.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MediaCrush
impact

Remote unauthenticated arbitrary file upload via /upload; potential RCE, data exposure, or persistence.

action required

Immediate action required

public exploits

Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
poc
automatable
yes
technical impact
total

Assessed by CISA 4 Feb 2026 (SSVC 2.0.3).

timeline

  1. 31 Jan 2026First proof-of-concept repository on GitHub (unvetted)
  2. 3 Feb 2026Published · 4 days later
  3. 4 Feb 2026CISA SSVC assessment: exploitation poc · 1 day later
  4. 4 Feb 2026CVE record last updated · same day later
  5. 5 Feb 2026Analysed by vulneraibility.com · same day later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
1 reference in the CVE record: 1 link

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved