CyberSecBulletin
CVE-2026-74881NVD status: Analyzed

openssl_encrypt: Permissive Cross-domain Security Policy with Untrusted Domains

Published Updated By the CyberSecBulletin desk

CVE-2026-74881 is a critical-severity permissive cross-domain security policy with untrusted domains vulnerability in openssl_encrypt from Jahlives, with a CVSS 3.1 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 1.4.0 as the first without the flaw, so updating openssl_encrypt to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update openssl_encrypt to 1.4.0 or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  4. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
Jahlivesopenssl_encryptbefore 1.4.01.4.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.07.1HighCNA (vulncheck.com)
CVSS 3.16.5MediumCNA (vulncheck.com)
CVSS 3.19.3CriticalNVD

Official description

openssl_encrypt versions before 1.4.0 configure CORS with allow_origins set to wildcard and allow_credentials enabled to true. Attackers can create malicious websites that make authenticated cross-origin requests to the API on behalf of any user who visits them.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Permissive Cross-domain Security Policy with Untrusted Domains

The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.

How developers prevent this class of flaw

  • Define a restrictive Content Security Policy or cross-domain policy file.
  • Avoid using wildcards in the CSP / cross-domain policy file. Any domain matching the wildcard expression will be implicitly trusted, and can perform two-way interaction with the target server.
  • For Flash, modify crossdomain.xml to use meta-policy options such as 'master-only' or 'none' to reduce the possibility of an attacker planting extraneous cross-domain policy files on a server.

More Permissive Cross-domain Security Policy with Untrusted Domains vulnerabilities (CWE-942)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in openssl_encrypt

All openssl_encrypt vulnerabilities

Recent Permissive Cross-domain Security Policy with Untrusted Domains vulnerabilities

Spotted an error? Tell us.