CVE Tools

CVE-2026-56711

VLC media player 3.0.0 through 3.0.23 memory corruption vulnerability

No known exploitation. EPSS puts it in the 3rd percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Steps

Written by AI from the record
  1. Check whether VLC media player is installed and identify its version.
  2. If it is 3.0.0 through 3.0.23, tell staff not to open unexpected media files with VLC.
  3. No fixed version has been published; ask your software vendor or IT provider to track and deploy the vendor’s update when available.
  4. Remove or isolate suspicious media attachments and downloads before users open them.

What it is

From the CVE record

VLC media player versions 3.0.0 through 3.0.23 contain a memory-safety vulnerability reachable when processing crafted media. Exploitation requires user interaction and may result in application termination or code execution with the privileges of the VLC process.

In plain language

Written by AI from the record

VLC media player 3.0.0 through 3.0.23 can be crashed or taken over if someone opens a malicious media file, so small businesses should treat unexpected media files as unsafe until a fix is available.

A high-severity local memory-corruption flaw (CWE-190/CWE-787) in VLC’s processing of crafted media files may cause application termination or code execution in the VLC process context.

If you're affected

  • Computer takeover risk
  • VLC application crashes
  • Work disruption
  • Data access risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS3rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.1% chance of exploitation activity in the next 30 days, which ranks it in the 3rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 9 days, from the signal feeds we watch.

  1. Record updated
  2. Record updated
  3. OpenVAS check added
  4. Publishedweakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Scored 7.0 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for VLC Media Player, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store