dbcve.org
Internet SecurityApplication · Bitdefender

CVE-2026-6851

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 27.0.58.315 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click 5 weeks old

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
An Improper link resolution before file access ('link following') vulnerability in the File Shredder module as used in Bitdefender Total Security and Internet Security on Windows allows a less-privileged local user to elevate rights by leveraging a race conditions via Symbolic Links. This issue affects Total Security: before 27.0.58.315; Internet Security: before 27.0.58.315.

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

A local privilege escalation vulnerability exists in Bitdefender's File Shredder module due to improper symbolic link resolution combined with race conditions. A less-privileged local user can exploit this to gain elevated rights by creating malicious symbolic links that the privileged File Shredder process follows.

MitigationUpgrade Bitdefender Total Security or Internet Security to version 27.0.58.315 or later. As a temporary control, restrict file system access for low-privileged users and monitor for unauthorized symlink creation in sensitive directories.

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
Internet SecurityApplication
Affected:< 27.0.58.315
Total SecurityApplication
Affected:< 27.0.58.315

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 Bitdefender product installation
    Check Programs and Features for Bitdefender Total Security or Internet Security, or look for Bitdefender processes (bdagent, vsserv, updater) in Task Manager
    Affected if Either Bitdefender Total Security or Internet Security is installed
  2. Determine installed Bitdefender version
    Open Bitdefender interface, navigate to Settings > About, or query the registry key HKLM\SOFTWARE\Bitdefender\General\ProductVersion
    Affected if Version is below 27.0.58.315
  3. Verify File Shredder module accessibility
    Check if the File Shredder feature is available to standard users. Attempt to locate the shredder.exe binary in the Bitdefender installation directory (typically under Program Files\Bitdefender\Bitdefender Security)
    Affected if File Shredder module exists and is accessible to non-admin users
  4. Audit for symlink creation activity
    Enable Windows Audit Policy for Object Access (Success/Failure) on sensitive directories. Use Sysmon Event ID 11 (FileCreate) or check Windows Security event logs for Event 4663 on directories like %SystemRoot%\System32
    Affected if Standard users are creating symbolic links in system directories
  5. Review user privileges on Bitdefender directories
    Check NTFS permissions on the Bitdefender installation folder and ensure standard users cannot write to directories used by the File Shredder service
    Affected if Non-privileged users have write access to Bitdefender directories that the privileged File Shredder process uses

The environment is affected if Bitdefender Total Security or Internet Security is installed with a version lower than 27.0.58.315 and the File Shredder module is accessible to standard users.

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
Upgrade available Upgrade to 27.0.58.315 or later
Fixed in 27.0.58.315
Interim mitigation

Upgrade Bitdefender Total Security or Internet Security to version 27.0.58.315 or later. As a temporary control, restrict file system access for low-privileged users and monitor for unauthorized symlink creation in sensitive directories.

Recommended fix High confidence

Bitdefender Total Security 27.0.58.315 or later; Bitdefender Internet Security 27.0.58.315 or later

  1. Open Bitdefender Total Security or Internet Security
  2. Navigate to Settings or the Protection section
  3. Check for updates or look for the version information
  4. Update to version 27.0.58.315 or later through the built-in update mechanism
  5. Alternatively, download the latest version from the official Bitdefender website and reinstall

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

Fix this in Internet Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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