JLSEC-2026-253

See a problem?
Please try reporting it to the source first.

Source

https://github.com/JuliaLang/SecurityAdvisories.jl/blob/main/advisories/published/2026/JLSEC-2026-253.md

Import Source

https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-253.json

JSON Data

https://api.osv.dev/v1/vulns/JLSEC-2026-253

Upstream

CVE-2024-6119

EUVD-2024-47266

GHSA-7m4m-pwhv-49c5

Published

2026-04-27T18:33:55.942Z

Modified

2026-04-27T19:02:32.034868784Z

Severity

7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CVSS Calculator

Summary

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server...

Details

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of service.

Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an otherName subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program.

Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Database specific

{
    "sources": [
        {
            "id": "CVE-2024-6119",
            "database_specific": {
                "status": "Analyzed"
            },
            "html_url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6119",
            "imported": "2026-04-27T16:32:47.154Z",
            "modified": "2025-06-03T10:51:54.117Z",
            "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2024-6119",
            "published": "2024-09-03T16:15:07.177Z"
        },
        {
            "imported": "2026-04-27T16:35:57.704Z",
            "modified": "2025-06-03T12:31:37Z",
            "url": "https://api.github.com/advisories/GHSA-7m4m-pwhv-49c5",
            "html_url": "https://github.com/advisories/GHSA-7m4m-pwhv-49c5",
            "id": "GHSA-7m4m-pwhv-49c5",
            "published": "2024-09-03T18:31:32Z"
        },
        {
            "id": "EUVD-2024-47266",
            "url": "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2024-47266",
            "html_url": "https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-47266",
            "imported": "2026-04-27T16:33:28.283Z",
            "modified": "2024-09-12T16:03:01Z",
            "published": "2024-09-03T15:58:06Z"
        }
    ],
    "license": "CC-BY-4.0"
}

References

Affected packages

Julia / OpenSSL_jll

Package

Name: OpenSSL_jll
Purl: pkg:julia/OpenSSL_jll?uuid=458c3c95-2e84-50aa-8efc-19380b2a3a95

Affected ranges

Type: SEMVER
Events: Introduced

3.0.8+0

Fixed

3.0.15+0

Database specific

source

"https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-253.json"