CVE-2026-74881: Permissive Cross-domain Security Policy with Untrusted Domains in jahlives openssl_encrypt
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.
AI Analysis
Technical Summary
The vulnerability in jahlives openssl_encrypt prior to version 1.4.0 involves an insecure CORS configuration where allow_origins is set to '*' (wildcard) and allow_credentials is enabled. This combination permits cross-origin requests with user credentials, enabling attackers to perform unauthorized actions by leveraging authenticated sessions of users who visit malicious websites. The CVSS 4.0 score is 7.1, indicating a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality.
Potential Impact
An attacker can exploit this vulnerability by hosting a malicious website that triggers authenticated cross-origin requests to the vulnerable API, potentially accessing or manipulating sensitive user data without authorization. This compromises user confidentiality and can lead to unauthorized actions performed in the context of the victim's session.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or update is available, it is recommended to avoid using versions of openssl_encrypt prior to 1.4.0 or to manually configure CORS policies to restrict allow_origins to trusted domains and disable allow_credentials if not necessary.
CVE-2026-74881: Permissive Cross-domain Security Policy with Untrusted Domains in jahlives openssl_encrypt
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.
CVSS v4.0
Score 7.1high
Affected software
pkg:github/jahlives/openssl_encryptRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in jahlives openssl_encrypt prior to version 1.4.0 involves an insecure CORS configuration where allow_origins is set to '*' (wildcard) and allow_credentials is enabled. This combination permits cross-origin requests with user credentials, enabling attackers to perform unauthorized actions by leveraging authenticated sessions of users who visit malicious websites. The CVSS 4.0 score is 7.1, indicating a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality.
Potential Impact
An attacker can exploit this vulnerability by hosting a malicious website that triggers authenticated cross-origin requests to the vulnerable API, potentially accessing or manipulating sensitive user data without authorization. This compromises user confidentiality and can lead to unauthorized actions performed in the context of the victim's session.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or update is available, it is recommended to avoid using versions of openssl_encrypt prior to 1.4.0 or to manually configure CORS policies to restrict allow_origins to trusted domains and disable allow_credentials if not necessary.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-17T10:36:18.506Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a82f003bf8831d539c48322
Added to database: 08/17/2026, 11:26:59 UTC
Last enriched: 08/17/2026, 11:43:10 UTC
Last updated: 08/17/2026, 13:16:32 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.