CVE Intelligence
Analysis AI-assisted

CVE-2026-74881: Jahlives openssl_encrypt before 1.4.0 CORS Misconfiguration via Wildcard Origins

Jahlives openssl_encrypt versions before 1.4.0 are described as configuring CORS with a wildcard allowed origin and credentials enabled. According to the record, this can let malicious websites make authenticated cross-origin requests to the API on behalf of visiting users. NVD rates it critical at 9.3 under CVSS 3.1, and the record shows it is not listed in CISA KEV.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-74881 describes a CORS misconfiguration in Jahlives openssl_encrypt versions before 1.4.0. The record states that CORS is configured with a wildcard allowed origin while credentials are enabled, a pattern classified under CWE-942 (Permissive Cross-domain Policy).

Impact

  • According to the record, a malicious website could make authenticated cross-origin requests to the API on behalf of a user who visits it.
  • NVD scores the issue 9.3 (Critical) under CVSS 3.1, with high confidentiality and integrity impact and user interaction required. VulnCheck scores it 6.5 under CVSS 3.1 and 7.1 under CVSS 4.0.
  • The specific data exposed depends on the API endpoints, which the record does not describe.

Affected products and versions

  • Product: Jahlives Openssl Encrypt, versions less than 1.4.0 according to the record.
  • The record does not list a separate fixed version. The boundary of the affected range is 1.4.0.

Exploitation status

  • The record shows this CVE is not listed in the CISA KEV catalog. No confirmed active exploitation appears in the sources consulted.
  • The SSVC fields in the record indicate exploitation none and automatable no.
  • The EPSS probability is 0.00363, with percentile 0.28327, dated 2026-10-13.

Remediation and mitigation

  • Review the vendor advisory GHSA-c65f-x25w-62jv, which the record lists as a mitigation reference.
  • Plan to move to version 1.4.0 or later, since the affected range is below that release. Confirm the exact remediation steps in the vendor advisory.
  • Until updated, restrict which origins can call the API and avoid permitting credentialed requests from broad or wildcard origins.

Detection guidance

  • Review server and API configuration for CORS settings that allow any origin together with credentials.
  • In a controlled test environment, check API responses for permissive origin and credentials headers appearing together.
  • Monitor logs for unexpected cross-origin requests to sensitive endpoints.

Limitations of the available information

  • The record does not identify which API endpoints or data are affected.
  • NVD and VulnCheck scores differ, and the record does not explain the difference.
  • The record does not state an explicit fixed version or patch. The GHSA advisory is referenced as a mitigation.
  • This analysis does not include exploit details.

Frequently asked questions

What versions of openssl_encrypt are affected by CVE-2026-74881?

According to the record, Jahlives Openssl Encrypt versions less than 1.4.0 are affected. The record does not list a separate fixed version, so review the vendor advisory for remediation details.

Is CVE-2026-74881 being actively exploited?

The record shows this CVE is not listed in CISA KEV, and no confirmed active exploitation appears in the sources consulted. The SSVC exploitation field is marked none.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.