CVE-2026-74876Network attack vector

Secret disclosure via unverified key import

Published Aug 17, 2026 · Updated Aug 17, 2026

Improper signature verification in jahlives openssl_encrypt before 1.4.0 allows attackers to disclose secrets via crafted key bundles. PublicKeyBundle.from_dict() in modules/key_bundle.py builds a bundle from untrusted dictionary data without validating its self_signature, and to_identity() can then convert that unverified bundle into an Identity object. Reachability depends on application code that accepts attacker-supplied bundle data and calls from_dict() followed by to_identity() without verify_signature(); the GitHub advisory notes that key_resolver.py verifies before use, so exposure is tied to direct use of the unguarded API path.

CVSS severity9.3
Critical
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper signature verification in jahlives openssl_encrypt before 1.4.0 allows attackers to disclose secrets via crafted key bundles. PublicKeyBundle.from_dict() in modules/key_bundle.py builds a bundle from untrusted dictionary data without validating its self_signature, and to_identity() can then convert that unverified bundle into an Identity object. Reachability depends on application code that accepts attacker-supplied bundle data and calls from_dict() followed by to_identity() without verify_signature(); the GitHub advisory notes that key_resolver.py verifies before use, so exposure is tied to direct use of the unguarded API path.

The record

CVE
CVE-2026-74876
Published
Aug 17, 2026
Updated
Aug 17, 2026
Vendor
jahlives
Product
OpenSSL Encrypt
Classifications
CWE-347
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 17, 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.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

jahlives · OpenSSL Encryptversion=0 <1.4.0

Published CVSS scores

9.3VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
9.8VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature

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