How severe is CVE-2026-74892?

CVE-2026-74892 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-74892 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-74892?

CVE-2026-74892 affects Jahlives Openssl Encrypt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-74892?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-74892 published?

CVE-2026-74892 was published on 2026-08-17 and last updated on 2026-08-31.

CVE-2026-74892

CVE-2026-74892 is a high-severity vulnerability in Jahlives Openssl Encrypt with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-798.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 8.7
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-798
Affected product: Jahlives Openssl Encrypt
Published: 2026-08-17
Last modified: 2026-08-31

Description

openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.

Frequently asked questions

What is CVE-2026-74892?: openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.
How severe is CVE-2026-74892?: CVE-2026-74892 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-74892 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-74892?: CVE-2026-74892 affects Jahlives Openssl Encrypt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-74892?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-74892 published?: CVE-2026-74892 was published on 2026-08-17 and last updated on 2026-08-31.

References

Affected products (1)

cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*

More vulnerabilities in Jahlives Openssl Encrypt

CVE-2026-81702 — Critical (CVSS 9.8): openssl_encrypt before 1.4.9 fails to re-derive and validate fingerprints when loading identities from identity.json,…
CVE-2026-81701 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.9 use a denylist to identify trusted built-in plugins, allowing unsigned plugins in…
CVE-2026-81700 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.9 contain a signature verification vulnerability in gpg_runner.verify_detached that…
CVE-2026-74901 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption…
CVE-2026-74900 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain a critical vulnerability in pqc.py where KEM decapsulation failures…
CVE-2026-74899 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain a sandbox escape vulnerability in IsolatedPluginExecutor that exposes…

All CVEs affecting Jahlives Openssl Encrypt →

Other CWE-798 (Use of Hard-coded Credentials) vulnerabilities

CVE-2026-18452 — Critical (CVSS 10.0): DMS+ (Non-Mobile) developed by Rich Source has a Use of Hard-coded Credentials vulnerability. Unauthenticated remote…
CVE-2026-45336 — Critical (CVSS 10.0): HireFlow is a web-based interview management system for managing candidates, scheduling interviews, and tracking hiring…
CVE-2026-13768 — Critical (CVSS 10.0): Gardyn devices expose a privileged iothubowner key. Access to this key will allow a malicious user to invoke an IoTHub…
CVE-2026-45631 — Critical (CVSS 10.0): Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.27.0 to before 0.29.3, a hardcoded…
CVE-2026-22769 — Critical (CVSS 10.0): Dell RecoverPoint for Virtual Machines, versions prior to 6.0.3.1 HF1, contain a hardcoded credential vulnerability.…
CVE-2025-42890 — Critical (CVSS 10.0): SQL Anywhere Monitor (Non-GUI) baked credentials into the code,exposing the resources or functionality to unintended…

Browse all CWE-798 (Use of Hard-coded Credentials) vulnerabilities →