Skip to main content
Mallory
UnratedVulnerability

CVE-2026-130506: Host out-of-bounds write in virglrenderer shader translation

Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-130506CWE-787

CVE-2026-130506 is an out-of-bounds write vulnerability in virglrenderer shader translation. A malicious guest virtual machine can submit a crafted pair of linked shaders that triggers a memory write outside the intended bounds in the host-side renderer. The corruption occurs during shader translation, before any OpenGL call is made. Debian Linux 12.0, 13.0, and 14.0 are listed as applicable platforms, although precise affected package versions are not specified.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation corrupts memory in the host-side rendering process, potentially causing process crashes, disruption of guest graphics, or compromise of the renderer's integrity. The assigned CVSS v3.0 assessment rates confidentiality, integrity, and availability impacts as high. Arbitrary code execution and complete guest-to-host escape are not specifically established by the available technical details.

Mitigation

If you can’t patch tonight, do this now.

Where operationally feasible, disable virglrenderer-backed accelerated graphics for untrusted guests or use a graphics configuration that does not invoke the affected shader translator. Restrict untrusted access to affected virtual machines and isolate host rendering processes to limit the consequences of memory corruption. These measures reduce exposure but do not correct the underlying flaw.

Remediation

Patch, then assume compromise.

No fixed package version or vendor patch is identified, and the vulnerability is listed as unpatched. Apply a vendor-provided virglrenderer security update when one becomes available; a specific upgrade target cannot currently be identified.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-130506 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-130506 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-130506?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-130506.
Is there a patch for CVE-2026-130506?
No fixed package version or vendor patch is identified, and the vulnerability is listed as unpatched. Apply a vendor-provided virglrenderer security update when one becomes available; a specific upgrade target cannot currently be identified.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.