Skip to main content
VulnerabilityPublished Updated

CVE-2026-74884: jahlives openssl_encrypt · External Control of File Name or Path

Affects jahlives openssl_encryptSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 1.4.0 soon.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:N/VA:N/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 14 Nov 2026.

What to do

Upgrade openssl_encrypt and jahlives/openssl_encrypt to 1.4.0.

Affected software

ProductAffectedFixed in
jahlivesopenssl_encryptAffected
  • <1.4.0
Fixed in
  • 1.4.0
GitHubjahlives/openssl_encryptpkg:github/jahlives/openssl_encryptOther threatsAffected
  • <1.4.0
Fixed in
  • 1.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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 remediate this vulnerability. Patch status is confirmed by the affectedVersions field indicating versions before 1.4.0 are vulnerable.

Description

openssl_encrypt versions before 1.4.0 contain a path traversal vulnerability in the _is_safe_path method where the plugin_id parameter is not sanitized before constructing the plugin config directory path. Attackers can declare a malicious plugin_id containing path traversal sequences like '../' to access arbitrary directories outside the intended plugin directory.

References

Community reviews

Loading reviews…