dbcve.org
NapocaApplication · Bitdefender

CVE-2026-10046

HIGH · 7.8 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Bitdefender Napoca bare-metal hypervisor contains an out-of-bounds write vulnerability in the BIOS INT 0x15 / E820 memory map handler, implemented in napoca/guests/bios_handlers.c. The handler computes a destination offset into the guest RealModeMemory buffer from guest-controlled ES and EDI register values without validating that the resulting address remains within the 1MB RealModeMemory allocation. A malicious guest operating in real mode can trigger the issue by invoking INT 0x15 with AX=0xE820, EDX=0x534D4150, ECX greater than or equal to 20, EBX=0, ES=0xFFFF, and EDI=0xFFFF. This can cause a write of up to 20 bytes past the end of the RealModeMemory buffer into the hypervisor heap. The product is end-of-life and unsupported when assigned.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Bitdefender Napoca hypervisor has an out-of-bounds write in its BIOS INT 0x15 E820 memory map handler (napoca/guests/bios_handlers.c). The handler computes a destination offset using guest-controlled ES and EDI registers without validating the address stays within the 1MB RealModeMemory buffer. A malicious real-mode guest can trigger this by setting ES=0xFFFF and EDI=0xFFFF with specific values in other registers, writing up to 20 bytes past the buffer into hypervisor heap memory.

MitigationThis vulnerability has no remediation as the product is end-of-life and unsupported. Organizations should remove any deployments of Bitdefender Napoca and migrate to a supported hypervisor solution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NapocaApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Bitdefender Napoca hypervisor is installed
    Check for Napoca hypervisor installation by looking for its executable or service: on Windows, check Program Files for 'Napoca' folder or run 'sc query' for Napoca services; on Linux, check /opt or /usr/lib for napoca components
    Affected if Napoca hypervisor software is present on the system
  2. Identify Napoca hypervisor processes
    Run process enumeration (tasklist on Windows, ps aux on Linux) and look for napoca-related processes such as napoca.exe, napoca-hypervisor, or similar
    Affected if Any Napoca hypervisor process is running
  3. Check for active virtual machines using E820
    Review running VM configurations to determine if guests that utilize BIOS E820 memory map queries are active. Any VM that boots and queries system memory map will trigger the vulnerable handler
    Affected if Any virtual machine is running on the Napoca hypervisor
  4. Confirm hypervisor handles real-mode memory queries
    The E820 handler is invoked when a guest queries BIOS memory map information. This occurs during VM boot for most guest operating systems. No special configuration needed - it's a default BIOS behavior
    Affected if The Napoca hypervisor is running any guest that performs memory map queries (standard BIOS behavior)
  5. Review guest execution policies
    Audit VM configurations to determine if untrusted or potentially malicious real-mode code could execute within guests
    Affected if Untrusted or unverified VMs are permitted to run on the Napoca hypervisor

If Bitdefender Napoca hypervisor is installed and running any virtual machines, the environment is affected since all versions contain the out-of-bounds write in the E820 memory map handler and no patch is available.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This vulnerability has no remediation as the product is end-of-life and unsupported. Organizations should remove any deployments of Bitdefender Napoca and migrate to a supported hypervisor solution.

Fix this in Napoca Scoped from the published advisory
  • Consultation2.0 h
2.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10046 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data