Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: opencryptoki-devel (AlmaLinux:10) 3.25.0-5.el10_1.2; opencryptoki (AlmaLinux:8) 3.22.0-3.el8_10.2; opencryptoki-ccatok (AlmaLinux:8) 3.22.0-3.el8_10.2.

Low priority for now. Upgrade to opencryptoki-devel (AlmaLinux:10) 3.25.0-5.el10_1.2; opencryptoki (AlmaLinux:8) 3.22.0-3.el8_10.2; opencryptoki-ccatok (AlmaLinux:8) 3.22.0-3.el8_10.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.8 · v3.1—No exploit Fix available
Published
Jan 21, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23893

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for opencryptoki project records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opencryptoki projectopencryptoki

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • opencryptoki project opencryptoki2.3.2 and later

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • opencryptoki opencryptoki

    • >= 2.3.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10opencryptoki-develbefore 3.25.0-5.el10_1.23.25.0-5.el10_1.2
AlmaLinux:8opencryptokibefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-ccatokbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-develbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-ep11tokbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-icatokbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-icsftokbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-libsbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-swtokbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:8opencryptoki-tpmtokbefore 3.22.0-3.el8_10.23.22.0-3.el8_10.2
AlmaLinux:9opencryptokibefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
AlmaLinux:9opencryptoki-ccatokbefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
AlmaLinux:9opencryptoki-develbefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
AlmaLinux:9opencryptoki-ep11tokbefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
AlmaLinux:9opencryptoki-icatokbefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
AlmaLinux:9opencryptoki-icsftokbefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
AlmaLinux:9opencryptoki-libsbefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
AlmaLinux:9opencryptoki-swtokbefore 3.25.0-4.el9_7.23.25.0-4.el9_7.2
Debian:12opencryptokifrom 0—
Debian:13opencryptokibefore 3.23.0+dfsg-0.3+deb13u13.23.0+dfsg-0.3+deb13u1
Debian:14opencryptokibefore 3.27.0-13.27.0-1
openSUSE:Leap 15.6openCryptokibefore 3.23.0-150600.3.14.13.23.0-150600.3.14.1
openSUSE:Leap 16.0openCryptokibefore 3.26.0-160000.1.13.26.0-160000.1.1
openSUSE:Leap 16.0openCryptokibefore 3.27.0-160000.1.13.27.0-160000.1.1

+96

Same product

opencryptoki project: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-40253openCryptoki: Memory safety vulnerabilities in BER/DER decoders in asn1.c
    24Monitor
  • CVE-2026-22791openCryptoki incorrectly calculates the buffer size in C_WrapKey with CKM_ECDH_AES_KEY_WRAP
    24Monitor
  • CVE-2012-4455openCryptoki 2.4.1 allows local users to create or set world-writable permissions on arbitrary files via a symlink attack on the (1) LCK..op
    24Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2012-4454Oct 10, 2012 · openCryptoki before 2.4.1, when using spinlocks, allows local users to create or set world-writable permissions on arbitrary files via a sym
    11Monitor
  • ← EarlierCVE-2021-3798Aug 23, 2022 · A flaw was found in openCryptoki.
    22Monitor
  • ← EarlierCVE-2024-0914Jan 31, 2024 · Opencryptoki: timing side-channel in handling of rsa pkcs#1 v1.5 padded ciphertexts (marvin)
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:opencryptoki3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
almalinux:opencryptoki-ccatok3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
almalinux:opencryptoki-devel3.25.0-5.el10_1.2 · AlmaLinux:10Package registry (OSV)
almalinux:opencryptoki-ep11tok3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
almalinux:opencryptoki-icatok3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
almalinux:opencryptoki-icsftok3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
almalinux:opencryptoki-libs3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
almalinux:opencryptoki-swtok3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
almalinux:opencryptoki-tpmtok3.22.0-3.el8_10.2 · AlmaLinux:8Package registry (OSV)
debian:opencryptoki3.23.0+dfsg-0.3+deb13u1 · Debian:13Package registry (OSV)
opensuse:openCryptoki3.23.0-150600.3.14.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:opencryptoki0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-ccatok0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-ccatok-debuginfo0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-debuginfo0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-debugsource0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-ep11tok0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-ep11tok-debuginfo0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-icatok0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-icatok-debuginfo0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-icsftok0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-icsftok-debuginfo0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:opencryptoki-libs0:3.25.0-5.el10_1.2 · Red Hat:enterprise_linux:10.1Package registry (OSV)
rocky linux:opencryptoki0:3.25.0-5.el10_1.2 · Rocky Linux:10Package registry (OSV)
suse:openCryptoki3.26.0-150700.5.12.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records