CVE-2025-52290

validatedZero produced an exploit or a check.

GHSA-wv9f-x489-g252 ↗EUVD-2025-211132 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
FFmpeg n/a
ETK-2026-2117Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1.2dTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+28h05magent stopped
0
+6h
+12h
+18h
+24h
+30h

description

FFmpeg build N-119856-gbe46370941 is reported to crash when handling specially formed media content. An attacker may cause a denial of service if they can make an affected FFmpeg process handle a crafted media file.

mitigation

Restrict processing of untrusted media and run FFmpeg workloads with isolation and restart supervision. Monitor upstream FFmpeg updates and upgrade when a release addressing this issue is identified.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.42%34th percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 00:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-19 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2025-52290

{
  "etk_id": "ETK-2026-2117",
  "cve_id": "CVE-2025-52290",
  "display_id": "CVE-2025-52290",
  "ghsa_id": "GHSA-wv9f-x489-g252",
  "euvd_id": "EUVD-2025-211132",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Null pointer dereference in FFmpeg H.264 handling",
  "summary": "FFmpeg build N-119856-gbe46370941 is reported to crash when handling specially formed media content. An attacker may cause a denial of service if they can make an affected FFmpeg process handle a crafted media file.",
  "mitigation": "Restrict processing of untrusted media and run FFmpeg workloads with isolation and restart supervision. Monitor upstream FFmpeg updates and upgrade when a release addressing this issue is identified.",
  "vendor": null,
  "product": "FFmpeg",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0042,
  "epss_percentile": 0.3489,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 24.214216383333333,
  "t0_at": "2026-10-19T00:00:00+00:00",
  "signals": {
    "check": {
      "at": "2026-10-20T04:04:31.584549+00:00",
      "days": 1.1698100063541668,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T00:00:00+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-19T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-52290"
    }
  }
}

published 2026-10-20 03:52Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.