CVE-2026-8148
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 · uneditedNAVER MYBOX Explorer for Windows before 3.0.11.160 allows a local attacker to escalate privileges to NT AUTHORITY\SYSTEM via registry manipulation due to improper privilege checks.
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 · moderate confidenceNAVER MYBOX Explorer for Windows versions prior to 3.0.11.160 contain a local privilege escalation vulnerability where attackers can manipulate Windows registry keys to gain NT AUTHORITY\SYSTEM privileges due to improper privilege validation during registry operations.
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< 3.0.11.160CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if NAVER MYBOX Explorer is installedOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or check C:\Program Files\Naver for the Mybox folder. Alternatively, run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Mybox*"}' in PowerShell.Affected if The application is not found in either location.
-
Determine installed versionIf installed, locate the version in the uninstall registry key (DisplayVersion value) or right-click the Mybox executable in Program Files and view Properties > Details for File Version.Affected if The displayed version is less than 3.0.11.160.
-
Identify registry keys used by MyboxRun Process Monitor or inspect HKCU\SOFTWARE\Naver or HKLM\SOFTWARE\Naver registry keys where the application stores configuration. Look for keys that the process writes to during normal operation.Affected if No registry keys under Naver folders exist or are readable.
-
Check registry key permissionsRight-click registry keys under HKLM\SOFTWARE\Naver or HKCU\SOFTWARE\Naver in Registry Editor, select Permissions, and verify which users have Write or Full Control permissions. Low-privilege users should not have write access to HKLM keys.Affected if Standard users have Write or Full Control permissions to registry keys in the Naver path.
-
Verify if Mybox service runs with elevated privilegesOpen Services, locate the Mybox service if present, right-click > Properties, and check the Log On account. Also run 'tasklist /svc' or check Task Manager to see if Mybox processes run as SYSTEM or a privileged account.Affected if The service or process runs under NT AUTHORITY\SYSTEM or another elevated account.
You are affected if NAVER MYBOX Explorer is installed with a version lower than 3.0.11.160 AND standard users can modify registry keys used by the application, allowing privilege escalation to SYSTEM.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.0.11.160
Upgrade NAVER MYBOX Explorer to version 3.0.11.160 or later; as a compensating control, restrict local access to trusted users only and monitor registry modifications in application-related paths.
3.0.11.160
- Identify the current installed version of NAVER MYBOX Explorer for Windows
- Navigate to the official NAVER MYBOX download page or update mechanism
- Download and install version 3.0.11.160 or later
- Verify the installation was successful by checking the version number in the application
- Confirm the patch addresses the privilege escalation vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8148 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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