CVE-2026-81690Hinoki check available

Code execution via skipped symlinked directory contents

Published Aug 27, 2026 · Updated Aug 27, 2026

Symlink following in OpenSSL Encrypt before 1.4.9 allows physically proximate attackers to execute code through a modified portable drive. The verify-usb v2 allowlist scan uses rglob(), which skips descent into symlinked directories, while O_NOFOLLOW protects only the final hash path component. A planted pycache/*.pyc file remains uncounted so verification reports PASSED, but execution requires the victim to run the portable install.

CVSS severity8.7
High
EPSS probability0.49%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Symlink following in OpenSSL Encrypt before 1.4.9 allows physically proximate attackers to execute code through a modified portable drive. The verify-usb v2 allowlist scan uses rglob(), which skips descent into symlinked directories, while O_NOFOLLOW protects only the final hash path component. A planted pycache/*.pyc file remains uncounted so verification reports PASSED, but execution requires the victim to run the portable install.

The record

CVE
CVE-2026-81690
Published
Aug 27, 2026
Updated
Aug 27, 2026
Vendor
jahlives
Product
OpenSSL Encrypt
Classifications
CWE-59, T1204.002
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 27, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 27, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.4.9

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

jahlives · OpenSSL Encryptversion=0 <1.4.9

Published CVSS scores

7.3VulnCheckCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
8.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-59Improper Link Resolution Before File Access ('Link Following')
T1204.002Malicious File

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo