Skip to content
Noroxi
CVE-2026-74876· NVD / CVE Program· CNA VulnCheck

openssl_encrypt before 1.4.0 Unverified Key Bundle Encryption

openssl_encrypt versions before 1.4.0 contain a vulnerability in PublicKeyBundle.from_dict() that creates key bundles from untrusted data without verifying signatures. Attackers can call from_dict() followed by to_identity() without signature verification to encrypt data using attacker-controlled public keys, leaking secrets.

CriticalCVSS 9.3 · v4.0—No exploit Fix available
Published
Aug 17, 2026
Updated
Oct 1, 2026
EPSS
0.3% · 26th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

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

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
jahlivesopenssl encrypt

Affected versions

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

  • jahlives openssl encryptbefore 1.4.0

Versions reported by the vendor

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

  • jahlives openssl_encrypt

    • 1.4.0not affected
    • before 1.4.0affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
PyPIopenssl-encryptbefore 1.4.01.4.0

Same product

jahlives: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-81719openssl_encrypt before 1.4.9 Remote Code Execution via Plugin
    37Monitor
  • CVE-2026-81717openssl_encrypt before 1.4.9 Integrity Bypass via Added Files
    37Monitor
  • CVE-2026-81714openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass
    37Monitor
  • CVE-2026-81706openssl_encrypt before 1.4.9 Key Substitution via Identity Shadowing
    37Monitor
  • CVE-2026-81702openssl_encrypt before 1.4.9 Key Substitution via Identity Load
    37Monitor
  • CVE-2026-81701openssl_encrypt before 1.4.9 Arbitrary Code Execution via unsigned plugin
    37Monitor

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
jahlives openssl_encrypt1.4.0Vendor (CNA)
PyPI:openssl-encrypt1.4.0Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

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

No commit or PR link among the references.

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.

  • CVE-2026-749010 days apartopenssl_encrypt before 1.4.0 Authentication Bypass via AES-CTR Fallback
    37Monitor
  • CVE-2026-8168010 days apartopenssl_encrypt before 1.4.9 Authentication Bypass via Recovery Slot Removal
    37Monitor
  • CVE-2026-8170010 days apartopenssl_encrypt before 1.4.9 GPG Signature Verification Bypass
    37Monitor
  • CVE-2026-8170110 days apartopenssl_encrypt before 1.4.9 Arbitrary Code Execution via unsigned plugin
    37Monitor
  • CVE-2026-8171410 days apartopenssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass
    37Monitor
  • CVE-2026-8171710 days apartopenssl_encrypt before 1.4.9 Integrity Bypass via Added Files
    37Monitor

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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

The bug in code

The whole CWE-347 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const claims = jwt.verify(token, publicKey);

Fixed

ts
const claims = jwt.verify(token, publicKey, {  algorithms: ["RS256"],  issuer: "https://id.example.com",  audience: "portal",});

Attack context

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

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

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

All records