BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-53938High confidence

OpenIDC/cjose has a heap buffer overflow in AES Key Wrap decryption (A128KW/A192KW/A256KW)

OpenIDC · cjose

Official source article: GitHub GHSA-75R7-F5CV-G3WJ ↗. Check the applicable product and release in the original source.

8.2HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.24% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs OpenIDC cjose and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcecjoseVendor fix publishedDebian records a fixed source-package version for this release.0.6.2.3-1+deb13u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcecjoseAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcecjoseVendor fix publishedDebian records a fixed source-package version for this release.0.6.2.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcecjoseVendor fix publishedDebian records a fixed source-package version for this release.0.6.2.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivecjoseUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-53938 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycjose: cjose: Heap buffer overflow in AES Key Wrap decryption leads to denial of service
7 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • cjose-devel as a component of Red Hat Enterprise Linux 10
  • cjose.src as a component of Red Hat Enterprise Linux 10
  • cjose-devel (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8
  • cjose.src (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8
  • cjose (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8
  • cjose as a component of Red Hat Enterprise Linux 9
  • cjose.src as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in cjose, a C library for Javascript Object Signing and Encryption (JOSE). A remote, unauthenticated attacker can exploit a heap buffer overflow vulnerability in the AES Key Wrap decryption process. By submitting a crafted Javascript Web Encryption (JWE) to an application, the attacker can trigger an out-of-bounds heap write. This can corrupt the heap, leading to a denial of service and potentially further memory corruption.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-74298

No EUVD known-exploited evidence

OpenIDC/cjose is a C library implementing the Javascript Object Signing and Encryption (JOSE). Prior to version 0.6.2.5, cjose's JWE decryption path for the AES Key Wrap key-management algorithms (`alg` = `A128KW`, `A192KW`, `A256KW`) does not validate the length of the attacker-supplied `encrypted_key` (JWE Encrypted Key) before unwrapping it into a fixed-size, heap-allocated Content Encryption Key (CEK) buffer. A remote, unauthenticated attacker who can submit a crafted JWE to an application that decrypts it with an AES-KW symmetric key can trigger an out-of-bounds heap write, corrupting the heap. This leads at minimum to a crash (denial of service) and, depending on the heap layout and allocator, may be leverageable for further memory-corruption impact. `cjose_jwe_import()` / `cjose_jwe_decrypt()` are pre-authentication entry points: they parse and process fully attacker-controlled input. Upgrade to cjose 0.6.2.5 to receive a patch. If upgrading is not immediately possible, reject the AES Key Wrap algorithms (`A128KW`/`A192KW`/`A256KW`) for untrusted JWEs at the application layer.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.2 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

OpenIDC/cjose is a C library implementing the Javascript Object Signing and Encryption (JOSE). Prior to version 0.6.2.5, cjose's JWE decryption path for the AES Key Wrap key-management algorithms (`alg` = `A128KW`, `A192KW`, `A256KW`) does not validate the length of the attacker-supplied `encrypted_key` (JWE Encrypted Key) before unwrapping it into a fixed-size, heap-allocated Content Encryption Key (CEK) buffer. A remote, unauthenticated attacker who can submit a crafted JWE to an application that decrypts it with an AES-KW symmetric key can trigger an out-of-bounds heap write, corrupting the heap. This leads at minimum to a crash (denial of service) and, depending on the heap layout and allocator, may be leverageable for further memory-corruption impact. `cjose_jwe_import()` / `cjose_jwe_decrypt()` are pre-authentication entry points: they parse and process fully attacker-controlled input. Upgrade to cjose 0.6.2.5 to receive a patch. If upgrading is not immediately possible, reject the AES Key Wrap algorithms (`A128KW`/`A192KW`/`A256KW`) for untrusted JWEs at the application layer.

What

OpenIDC/cjose is a C library implementing the Javascript Object Signing and Encryption (JOSE). Prior to version 0.6.2.5, cjose's JWE decryption path for the AES Key Wrap key-management algorithms (`alg` = `A128KW`, `A192KW`, `A256KW`) does not validate the length of the attacker-supplied `encrypted_key` (JWE Encrypted Key) before unwrapping it into a fixed-size, heap-allocated Content Encryption Key (CEK) buffer. A remote, unauthenticated attacker who can submit a crafted JWE to an application that decrypts it with an AES-KW symmetric key can trigger an out-of-bounds heap write, corrupting the heap. This leads at minimum to a crash (denial of service) and, depending on the heap layout and allocator, may be leverageable for further memory-corruption impact. `cjose_jwe_import()` / `cjose_jwe_decrypt()` are pre-authentication entry points: they parse and process fully attacker-controlled input. Upgrade to cjose 0.6.2.5 to receive a patch. If upgrading is not immediately possible, reject the AES Key Wrap algorithms (`A128KW`/`A192KW`/`A256KW`) for untrusted JWEs at the application layer.

Why

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

OpenIDC/cjose is a C library implementing the Javascript Object Signing and Encryption (JOSE). Prior to version 0.6.2.5, cjose's JWE decryption path for the AES Key Wrap key-management algorithms (`alg` = `A128KW`, `A192KW`, `A256KW`) does not validate the length of the attacker-supplied `encrypted_key` (JWE Encrypted Key) before unwrapping it into a fixed-size, heap-allocated Content Encryption Key (CEK) buffer. A remote, unauthenticated attacker who can submit a crafted JWE to an application that decrypts it with an AES-KW symmetric key can trigger an out-of-bounds heap write, corrupting the heap. This leads at minimum to a crash (denial of service) and, depending on the heap layout and allocator, may be leverageable for further memory-corruption impact. `cjose_jwe_import()` / `cjose_jwe_decrypt()` are pre-authentication entry points: they parse and process fully attacker-controlled input. Upgrade to cjose 0.6.2.5 to receive a patch. If upgrading is not immediately possible, reject the AES Key Wrap algorithms (`A128KW`/`A192KW`/`A256KW`) for untrusted JWEs at the application layer.

Why

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Heap-based Buffer Overflow → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-122 ↗

CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-122
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-74298Official EUVD mapping

OpenIDC/cjose is a C library implementing the Javascript Object Signing and Encryption (JOSE). Prior to version 0.6.2.5, cjose's JWE decryption path for the AES Key Wrap key-management algorithms (`alg` = `A128KW`, `A192KW`, `A256KW`) does not validate the length of the attacker-supplied `encrypted_key` (JWE Encrypted Key) before unwrapping it into a fixed-size, heap-allocated Content Encryption Key (CEK) buffer. A remote, unauthenticated attacker who can submit a crafted JWE to an application that decrypts it with an AES-KW symmetric key can trigger an out-of-bounds heap write, corrupting the heap. This leads at minimum to a crash (denial of service) and, depending on the heap layout and allocator, may be leverageable for further memory-corruption impact. `cjose_jwe_import()` / `cjose_jwe_decrypt()` are pre-authentication entry points: they parse and process fully attacker-controlled input. Upgrade to cjose 0.6.2.5 to receive a patch. If upgrading is not immediately possible, reject the AES Key Wrap algorithms (`A128KW`/`A192KW`/`A256KW`) for untrusted JWEs at the application layer.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3626Red Hat Enterprise Linux (cjose): Schwachstelle ermöglicht Denial of Service und Manipulation von Daten

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux (cjose) ausnutzen, um einen Denial of Service Angriff durchzuführen, und um Daten zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260916Security Bulletin 16 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 16 Sep 2026, published on 16 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 8 Sept 2026 · Last source change 9 Sept 2026, 16:03 UTC · CWE-122 · Heap-based Buffer Overflow

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-09
European sourceENISA EUVD · EUVD-2026-74298
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 0.6.2.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 0.6.2.5 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-53938 to remediation: access.redhat.com/CVE-2026-53938.
    Before
    remediation: access.redhat.com/CVE-2026-53938
    After
    remediation: access.redhat.com/CVE-2026-53938
    Red Hat Product Security ↗
  4. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    cjose-devel as a component of Red Hat Enterprise Linux 10; cjose.src as a component of Red Hat Enterprise Linux 10; cjose-devel (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8; cjose.src (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8; cjose (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8; cjose as a component of Red Hat Enterprise Linux 9; cjose.src as a component of Red Hat Enterprise Linux 9
    After
    cjose-devel as a component of Red Hat Enterprise Linux 10; cjose.src as a component of Red Hat Enterprise Linux 10; cjose-devel (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8; cjose.src (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8; cjose (mod_auth_openidc:2.3) as a component of Red Hat Enterprise Linux 8; cjose as a component of Red Hat Enterprise Linux 9; cjose.src as a component of Red Hat Enterprise Linux 9 · Fixed: cjose-0:0.6.2.2-7.el10_0.1.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-0:0.6.2.2-7.el10_0.1.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-0:0.6.2.2-7.el10_0.1.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-0:0.6.2.2-7.el10_0.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-0:0.6.2.2-7.el10_0.1.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debuginfo-0:0.6.2.2-7.el10_0.1.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debuginfo-0:0.6.2.2-7.el10_0.1.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debuginfo-0:0.6.2.2-7.el10_0.1.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debuginfo-0:0.6.2.2-7.el10_0.1.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debugsource-0:0.6.2.2-7.el10_0.1.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debugsource-0:0.6.2.2-7.el10_0.1.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debugsource-0:0.6.2.2-7.el10_0.1.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-debugsource-0:0.6.2.2-7.el10_0.1.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); cjose-0:0.6.1-13.el9_2.1.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-0:0.6.1-13.el9_2.1.i686 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-0:0.6.1-13.el9_2.1.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-0:0.6.1-13.el9_2.1.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-0:0.6.1-13.el9_2.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-0:0.6.1-13.el9_2.1.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debuginfo-0:0.6.1-13.el9_2.1.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debuginfo-0:0.6.1-13.el9_2.1.i686 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debuginfo-0:0.6.1-13.el9_2.1.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debuginfo-0:0.6.1-13.el9_2.1.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debuginfo-0:0.6.1-13.el9_2.1.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debugsource-0:0.6.1-13.el9_2.1.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debugsource-0:0.6.1-13.el9_2.1.i686 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debugsource-0:0.6.1-13.el9_2.1.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debugsource-0:0.6.1-13.el9_2.1.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-debugsource-0:0.6.1-13.el9_2.1.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); cjose-0:0.6.1-16.el9_4.1.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); and 58 more
    Red Hat Product Security ↗
  6. ENISA EUVD mappingEUVD-2026-74298 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-74298"}
    ENISA EUVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-74298↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-75R7-F5CV-G3WJ↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-53938 · cve.blacktree.nl