LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23893: openCryptoki has improper link resolution before file access (link following)

openCryptoki is a PKCS#11 library and provides tooling for Linux and AIX. Versions 2.3.2 and above are vulnerable to symlink-following when running in privileged contexts. A token-group user can redirect file operations to arbitrary filesystem targets by planting symlinks in group-writable token directories, resulting in privilege escalation or data exposure. Token and lock directories are 0770 (group-writable for token users), so any token-group member can plant files and symlinks inside them. When run as root, the base code handling token directory file access, as well as several openCryptoki tools used for administrative purposes, may reset ownership or permissions on existing files inside the token directories. An attacker with token-group membership can exploit the system when an administrator runs a PKCS#11 application or administrative tool that performs chown on files inside the token directory during normal maintenance. This issue is fixed in commit 5e6e4b4, but has not been included in a released version at the time of publication.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-23893 affects openCryptoki on Linux and AIX. A user who already belongs to a token group can place symlinks in group-writable token directories. If an administrator later runs affected openCryptoki tools or applications as root, file ownership or permissions may be changed on unintended files, causing privilege escalation or sensitive data exposure.

Executive priority

Treat as a targeted local privilege risk, not an internet-wide emergency. Prioritize systems where token-group membership is broad, where openCryptoki is used for sensitive cryptographic operations, or where administrators routinely run maintenance tools as root.

Technical view

openCryptoki versions 2.3.2 and later have CWE-59 improper link resolution before file access. Token and lock directories are 0770, allowing token-group members to create symlinks. Privileged code and administrative tools may follow those symlinks during normal file operations such as chown. CVSS is 6.8, local attack vector, low complexity, low privileges, and required user interaction.

Likely exposure

Exposure is limited to systems running openCryptoki 2.3.2 or later where untrusted or lower-privileged users have token-group membership. Risk increases when administrators run PKCS#11 applications or openCryptoki administrative tools as root against token directories.

Exploitation context

Sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires local token-group access plus an administrative or privileged action that touches files in the affected directories. The impact can include privilege escalation, file permission changes, or data exposure.

Researcher notes

The public advisory states the fix exists in commit 5e6e4b4 but was not included in a released version at publication. Evidence supports local exploitation conditions and symlink-following impact, but no public source here confirms exploitation in the wild or a packaged release containing the fix.

Mitigation direction

  • Review openCryptoki advisory GHSA-j6c7-mvpx-jx5q for current vendor guidance.
  • Track whether commit 5e6e4b4 is included in an official release or downstream package.
  • Restrict token-group membership to trusted users only.
  • Avoid running affected administrative tools as root unless operationally necessary.
  • Monitor token and lock directories for unexpected symlinks or files.

Validation and detection

  • Inventory hosts running openCryptoki and record installed versions.
  • Identify systems with openCryptoki version 2.3.2 or later.
  • Review token-group membership for untrusted or unnecessary accounts.
  • Check whether vendor packages include commit 5e6e4b4 or equivalent fix.
  • Inspect token and lock directories for symlinks created by non-administrative users.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-59: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23893 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L1.35.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2026-23893Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
opencryptokiopencryptoki>= 2.3.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-59 · source CWE mapping

Improper Link Resolution Before File Access ('Link Following')

Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.