Skip to content

NetworksCritical 9.0

CVE-2026-65094

VM can trigger write-what-where in NVIDIA Virtio‑Net on BlueField, enabling code execution.

How scary is it?

updated 22 Nov 2026
  • No

    Works without logging in1

    Needs a login: a basic user account (CVSS PR:L).

  • No

    Reachable over the network1

    Needs access to the same local network (CVSS AV:A).

  • Yes

    Proof-of-concept code is public2

    1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 4 products in an affected versionNVIDIA VIRTIO-Net GA / NVIDIA VIRTIO-Net LTS23 / NVIDIA VIRTIO-Net LTS24 (+1 more)

    NVIDIA VIRTIO-Net GA: All versions prior to 25.10.6

    NVIDIA VIRTIO-Net LTS23: 1.7.21 and older versions

    NVIDIA VIRTIO-Net LTS24: All versions prior to 24.10.50

    NVIDIA VIRTIO-Net LTS25: All versions prior to 25.10.2

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker is on the same local network

    CVSS attack vector: Adjacent (AV:A). Same subnet or link layer.

    Source 1

  3. The attacker has a user account

    CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Recommendation, AI-writtenIsolate affected DPUs, block untrusted VMs, apply vendor patch when available.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

CVSS
9.0Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.34%chance of exploitation in the next 30 daystop 73% of scored CVEsFIRST score of 21 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
20 Nov 2026analysed here 21 Nov 2026

Summary

Impact

Guest VM can cause a write-what-where (CWE-123) in Virtio‑Net, enabling code execution in Virtio‑Net/DPU context and potential VM escape or host/DPU compromise.

Triage

Exploitable
At runtime
Attack vector
adjacent network
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
NVIDIA VIRTIO-Net GAAll versions prior to 25.10.6Vendor says fixed in: not stated
NVIDIA VIRTIO-Net LTS231.7.21 and older versionsVendor says fixed in: not stated
NVIDIA VIRTIO-Net LTS24All versions prior to 24.10.50Vendor says fixed in: not stated
NVIDIA VIRTIO-Net LTS25All versions prior to 25.10.2Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • NVIDIA BlueField DPUs
  • Virtio‑Net driver on BlueField
  • VMs using Virtio network on affected DPUs

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability is triggered by a virtual machine sending data over the Virtio network driver, which is not an HTTP-based protocol. Therefore, a web application firewall cannot filter or block the malicious input.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 20 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

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.

Timeline

  1. 20 Nov 2026Published
  2. 20 Nov 2026CISA SSVC assessment: exploitation none1 day later
  3. 20 Nov 2026CVE record last updatedsame day later
  4. 21 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
  5. 21 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-65094 being exploited?

Not confirmed. CVE-2026-65094 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.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-65094?

CVE-2026-65094 is rated Critical with a CVSS score of 9.0. 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-2026-65094?

Not known from our data. No patch reference has been recorded for CVE-2026-65094, 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-2026-65094 affect?

CVE-2026-65094 affects NVIDIA BlueField DPUs, Virtio‑Net driver on BlueField, VMs using Virtio network on affected DPUs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-65094?

Isolate affected DPUs, block untrusted VMs, apply vendor patch when available.

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

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Other links (3)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.