JLSEC-2026-273
Record from OSV · Published April 27, 2026
Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires the `X509_V_FLAG_USE_DELTAS` flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the `EXFLAG_FRESHEST` flag set, and an attacker to provide a malformed CRL to an application that processes it. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| AppBundler | pkg.julialang.org | 1.0.1 |
| OpenSSL_jll | pkg.julialang.org | 3.5.6+0, 3.0.20+0 |
| OpenSSL_jll | juliahub.com | 3.5.6+0, 3.0.20+0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Julia | Openresty_jll | 0 |
| Julia | Openresty_jll | 0 |
| Julia | AppBundler | 1.0.0, 1.0.0 |
| Julia | OpenSSL_jll | 0, 3.5.0+0 |
| Julia | OpenSSL_jll | 0, 3.5.0+0 |
| Julia | AppBundler | 1.0.0 |
Timeline
- Apr 27, 2026 CVE Published
- Aug 13, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln JLSEC-2026-273
vulnetix vdb fixes JLSEC-2026-273
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/JLSEC-2026-273/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html url
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html url
- https://github.com/openssl/openssl/commit/59c3b3158553ab53275bbbccca5cb305d591cf2e url
- https://github.com/openssl/openssl/commit/5a0b4930779cd2408880979db765db919da55139 url
- https://github.com/openssl/openssl/commit/602542f2c0c2d5edb47128f93eac10b62aeeefb3 url
- https://github.com/openssl/openssl/commit/a9d187dd1000130100fa7ab915f8513532cb3bb8 url
- https://github.com/openssl/openssl/commit/d3a901e8d9f021f3e67d6cfbc12e768129862726 url
- https://openssl-library.org/news/secadv/20260407.txt url