dbcve.org
NapocaApplication · Bitdefender

CVE-2026-10047

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
The Bitdefender Napoca bare-metal hypervisor contains an out-of-bounds write vulnerability in the real-mode hook handler, implemented in napoca/kernel/handler.c. The handler uses a guest-controlled SS:SP-derived offset as an index into the 1MB RealModeMemory buffer without bounds validation. With SS=0xFFFF and ESP=0xFFFF, the computed offset can reach 0x10FFEF, exceeding the RealModeMemory buffer by 65,519 bytes. The IRET frame push can therefore write past the end of the 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 contains an out-of-bounds write vulnerability in the real-mode hook handler (napoca/kernel/handler.c). The handler uses guest-controlled SS:SP register values to compute an offset into the 1MB RealModeMemory buffer without any bounds validation. By setting SS=0xFFFF and ESP=0xFFFF, an attacker can cause writes 65,519 bytes beyond the buffer boundary, corrupting the hypervisor heap via the IRET frame push.

MitigationThis product is end-of-life and unsupported with no patch available; organizations should migrate to a supported hypervisor solution. If continued use is mandatory, implementing strict bounds checking on the SS:SP-derived offset before memory access would be required.

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. Identify if Bitdefender Napoca hypervisor is installed
    Search for Napoca hypervisor installation directories, executables, or services. Common paths may include 'Napoca', 'bitdefender-napoca', or similar naming in program files, system directories, or hypervisor management tools.
    Affected if The hypervisor is present on the system, as all versions are affected by the vulnerability.
  2. Locate the real-mode hook handler source or binary
    Search for the file 'handler.c' in paths containing 'napoca/kernel/' within the Napoca installation directory or source tree.
    Affected if The handler file exists, confirming the vulnerable component is present.
  3. Verify the RealModeMemory buffer allocation
    Inspect the hypervisor binary or configuration for the RealModeMemory buffer allocation (1MB size). This may be visible in memory dumps, binary strings, or configuration files.
    Affected if The 1MB RealModeMemory buffer is allocated, which the vulnerability writes beyond.
  4. Determine if guest VMs can control SS and ESP registers
    Check hypervisor configuration or documentation to confirm that guest virtual machines can set SS=0xFFFF and ESP=0xFFFF in real mode, enabling the offset calculation of 0x10FFEF.
    Affected if Guest VMs can control SS:SP registers to the specific values (SS=0xFFFF, ESP=0xFFFF), which triggers the out-of-bounds condition.

If Bitdefender Napoca hypervisor is installed and running guest VMs with real-mode execution capability, the system is affected because all versions contain the unbounded SS:SP offset calculation in the real-mode hook handler.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This product is end-of-life and unsupported with no patch available; organizations should migrate to a supported hypervisor solution. If continued use is mandatory, implementing strict bounds checking on the SS:SP-derived offset before memory access would be required.

Recommended fix High confidence
  1. No remediation steps available. The Bitdefender Napoca hypervisor is end-of-life and unsupported according to the official description. There is no vendor-provided patch, update, or upgrade path for this vulnerability.
Caveat Product is end-of-life and unsupported. No further vendor support available.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Napoca Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10047 — 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-10047 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