dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-58583

HIGH · 7.1 CVSS v3.1 Published 2026-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click 7 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
FluxInk (formerly Sunia SPB Peripheral) Color Management Driver (TcnPeripheral64.sys) 1.0.7.2 allows local privilege escalation for a standard user account via arbitrary physical memory mapping at \Device\PhysicalMemory. Fixed in version 1.0.7.6. The fixed driver is currently available in the Windows 11 25H2 HLK (Hardware Lab Kit). The fixed driver may be available through Windows Update or from Lenovo directly.

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 FluxInk Color Management Driver (TcnPeripheral64.sys) version 1.0.7.2 contains a local privilege escalation vulnerability allowing standard users to map arbitrary physical memory through \Device\PhysicalMemory, bypassing intended access controls and enabling kernel-level code execution.

MitigationUpgrade the TcnPeripheral64.sys driver to version 1.0.7.6 or later, available via Windows 11 25H2 HLK, Windows Update, or directly from Lenovo.

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

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
None

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

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. Locate the TcnPeripheral64.sys driver file
    Search for TcnPeripheral64.sys in standard Windows driver directories such as C:\Windows\System32\drivers\ and C:\Windows\System32\DriverStore\FileRepository\. Use File Explorer search or run: Get-ChildItem -Path C:\Windows\System32\drivers -Filter TcnPeripheral64.sys -Recurse -ErrorAction SilentlyContinue
    Affected if The driver file is found on the system at any location, indicating the FluxInk Color Management Driver is installed
  2. Retrieve the driver file version
    Right-click the TcnPeripheral64.sys file, select Properties, then view the Details tab to see the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Windows\System32\drivers\TcnPeripheral64.sys').VersionInfo.FileVersion
    Affected if The version number is lower than 1.0.7.6, or the version cannot be determined (older version format)
  3. Check if the driver is currently loaded
    Open an elevated command prompt or PowerShell and run: Get-Process | Where-Object {$_.Name -match 'TcnPeripheral'} or check services: Get-Service | Where-Object {$_.Name -match 'TcnPeripheral'}. Also check device manager for the driver under System devices.
    Affected if The driver is listed as loaded or running as a service, meaning the attack surface is active
  4. Verify PhysicalMemory device access policy
    Check if standard users can access \Device\PhysicalMemory by reviewing driver documentation or testing with a standard user account attempting to open \Device\PhysicalMemory. In an administrative PowerShell session, verify the driver's ACLs if accessible via tools like WinObj.
    Affected if The driver permits unprivileged or standard user access to map physical memory, which is the core vulnerability condition

A user is affected if TcnPeripheral64.sys version 1.0.7.6 or later is NOT installed and the driver is loaded or loadable on the system, allowing standard users to map physical memory.

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

Upgrade the TcnPeripheral64.sys driver to version 1.0.7.6 or later, available via Windows 11 25H2 HLK, Windows Update, or directly from Lenovo.

Recommended fix High confidence

TcnPeripheral64.sys version 1.0.7.6

  1. Identify the TcnPeripheral64.sys driver on the affected system
  2. Check the current driver version (should show 1.0.7.2 for vulnerable instances)
  3. Obtain the fixed driver version 1.0.7.6 from one of these sources: Windows Update (if available), Lenovo support website directly, or Windows 11 25H2 HLK (Hardware Lab Kit)
  4. Install the updated driver following Lenovo's standard driver update procedure
  5. Verify the installed driver version is 1.0.7.6 or later using Device Manager or driver enumeration tools
  6. Confirm the vulnerability is remediated by verifying standard user accounts can no longer map arbitrary physical memory
Caveat Driver updates may require system restart; ensure compatibility with other Lenovo peripheral software

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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