Skip to main content
VulnerabilityPublished Updated

CVE-2026-74880: jahlives openssl_encrypt · Use of GET Request Method With Sensitive Query Strings

Affects jahlives openssl_encryptSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.4.0 as a priority.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade jahlives openssl_encrypt to 1.4.0.

Affected software

ProductAffectedFixed in
jahlivesopenssl_encryptAffected
  • <1.4.0
Fixed in
  • 1.4.0

AI-suggested

A fix is available in jahlives openssl_encrypt version 1.4.0 and later. Users should upgrade to version 1.4.0 or newer to eliminate the vulnerability. Avoid passing sensitive tokens in URL query parameters to prevent exposure through logs and browser histories.

Description

CVE-2026-74880 is a critical vulnerability in jahlives openssl_encrypt versions before 1.4.0 where refresh tokens are accepted as URL query parameters in keyserver and telemetry server routes. This design allows attackers to extract sensitive tokens from server logs, proxy logs, browser history, and HTTP Referer headers, potentially leading to unauthorized access.

References

Community reviews

Loading reviews…