jackson-dataformats-binary: CBOR parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of service
FasterXML · jackson-dataformats-binary
7.5HighCVSS 3.1
Recommended action
Within 7 days
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 1 Oct 2026
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.56% 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.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs FasterXML jackson-dataformats-binary and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
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
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 release
Source package
Vendor state
Fixed version
Evidence
Debian trixietrixie · source
jackson-dataformat-cbor
Not affectedDebian marks this release not affected (fixed-version marker 0).
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
2 current
CVE-2026-68495 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycom.fasterxml.jackson.dataformat/jackson-dataformat-cbor: jackson-dataformat-cbor: Denial of Service via excessively long property names
1 known not affected
The vendor explicitly states that these products are not affected by this CVE.
All currently supported Red Hat products
Summary
A flaw was found in jackson-dataformat-cbor. The parser fails to enforce maximum property name length limits when decoding Concise Binary Object Representation (CBOR) documents. A remote attacker can exploit this vulnerability by submitting a crafted CBOR document containing an excessively long property name. Processing this input causes unbounded memory allocation, leading to heap exhaustion and a Denial of Service (DoS).
The vendor explicitly identifies these products as affected by this CVE.
jackson-dataformat-xml as component of SUSE Linux Enterprise Desktop 15 SP7
jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP2
jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP2
jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP3
jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP3
jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4
jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5
jackson-dataformat-xml as component of SUSE Linux Enterprise Module for Basesystem 15 SP7
jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP2-LTSS
jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP2-LTSS
Summary
The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-90977
No EUVD known-exploited evidence
The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.
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
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available
01
What, why and how
The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.
What
The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.
Why
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
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
The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.
Why
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
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.Reference recorded
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
Likely attack path
a network path → Allocation of Resources Without Limits or Throttling → 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-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
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:N/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.INoneIntegrity impact: No direct loss is represented by this metric.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-770Public exploit reference
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-90977Official EUVD mapping
The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.
Official EUVD record ↗BSI · German · WID-SEC-2026-4634Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye und Jira): Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.
Official advisory ↗BSI · German · WID-SEC-2026-4056Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye und Jira): Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Crucible, Fisheye und Jira ausnutzen, um Daten zu manipulieren, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um einen Cross-Site Scripting Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um beliebigen Programmcode auszuführen.
Official advisory ↗BSI · German · WID-SEC-2026-3702FasterXML Jackson: Mehrere Schwachstellen ermöglichen Denial of Service
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in FasterXML Jackson ausnutzen, um einen Denial of Service Angriff durchzuführen.
Official advisory ↗Cyber Security Agency of Singapore · English · CSA-SB-20261007Security Bulletin 7 Oct 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 7 Oct 2026, published on 7 October 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Official advisory ↗NCSC-NL · Dutch · NCSC-2026-0496Kwetsbaarheden verholpen in Atlassian producten
FasterXML jackson-dataformats-binary's CBOR and Smile parsers fail to enforce maxNameLength limits on JSON object property names, enabling attackers to cause memory exhaustion and denial of service, tracked as CVE-2026-68495 and CVE-2026-68496 respectively.
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.
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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.
Official vendor articles3 stored documents
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
Security Bulletin - October 20 2026 | Atlassian Support | Atlassian Documentation →Original publisher ↗Searchable text snapshot · Captured 22 Nov 2026Unable to load
Security Bulletin - October 20 2026
Security Advisories & Bulletins
November 2022: Atlassian Security Advisories Overview
Archived Security Advisories
Security Advisories for Apps
July 2022: Atlassian Security Advisories Overview
August 2022: Atlassian Security Advisories Overview
January 2023: Secu
Security Bulletin - November 17 2026 | Atlassian Support | Atlassian Documentation →Original publisher ↗Searchable text snapshot · Captured 19 Nov 2026Unable to load
Security Bulletin - November 17 2026
Security Advisories & Bulletins
November 2022: Atlassian Security Advisories Overview
Archived Security Advisories
Security Advisories for Apps
July 2022: Atlassian Security Advisories Overview
August 2022: Atlassian Security Advisories Overview
January 2023: Sec
CVE-2026-68495 Common Vulnerabilities and Exposures | SUSE →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026CVE-2026-68495
Common Vulnerabilities and Exposures
[Previous] [Index] [Next]
Upstream information
CVE-2026-68495 at MITRE
Description
SUSE information
Overall state of this security issue: Pending
This issue is currently rated as having important severity.
CVSS v3 Scores
CVSS detail SUSE
Base Score 7.5
Vector CV
04
Evidence and provenance
Published 1 Oct 2026 · Last source change 1 Oct 2026, 18:16 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling
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-10-02
European sourceENISA EUVD · EUVD-2026-90977
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
jackson-dataformat-cbor as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-dataformat-xml as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-dataformats-binary as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-dataformat-xml as component of SUSE Linux Enterprise Module for Basesystem 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise Module for Development Tools 15 SP7; jackson-dataformats-binary as component of SUSE Linux Enterprise Module for Development Tools 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP2; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP2; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP3; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP3; and 39 more
After
jackson-dataformat-xml as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-dataformat-xml as component of SUSE Linux Enterprise Module for Basesystem 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP2; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP2; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP3; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP3; jackson-dataformat-xml as component of SUSE Linux Enterprise Server 15 SP4-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise Server 15 SP4; jackson-dataformat-xml as component of SUSE Linux Enterprise Server 15 SP5-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise Server 15 SP5; jackson-dataformat-xml as component of SUSE Linux Enterprise Server 15 SP6-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise Server 15 SP6; jackson-dataformat-xml as component of SUSE Linux Enterprise Server 15 SP7; jackson-dataformat-xml as component of SUSE Linux Enterprise Server Teradata 15 SP4; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server for SAP Applications 15 SP2; jackson-dataformats-binary as component of SUSE Linux Enterprise Server for SAP Applications 15 SP2; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server for SAP Applications 15 SP3; jackson-dataformats-binary as component of SUSE Linux Enterprise Server for SAP Applications 15 SP3; and 4 more
Affected versionsThe structured affected or fixed version information changed.
Before
jackson-dataformat-cbor as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-dataformat-xml as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-dataformats-binary as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-dataformat-xml as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-dataformats-binary as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-dataformat-xml as component of SUSE Linux Enterprise Module for Basesystem 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise Module for Development Tools 15 SP7; jackson-dataformats-binary as component of SUSE Linux Enterprise Module for Development Tools 15 SP7; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP2; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP2; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-dataformat-cbor as component of SUSE Linux Enterprise Server 15 SP3; jackson-dataformats-binary as component of SUSE Linux Enterprise Server 15 SP3; and 39 more · Fixed: The vendor publishes a fix, but no concise fixed-product list is available in this advisory.
After
jackson-dataformats-binary: 2.16.0 ≤ 2.18.9, 2.19.0 ≤ 2.21.5, 2.22.0 ≤ 2.22.1, 3.0.0 ≤ 3.1.5, 3.2.0 ≤ 3.2.1 · Fixed: Upgrade to com.fasterxml.jackson.dataformat:jackson-dataformat-cbor 2.18.10, 2.21.6 or 2.22.2, or to tools.jackson.dataformat:jackson-dataformat-cbor 3.1.6 or 3.2.2. The 2.16.x, 2.17.x, 2.19.x, 2.20.x and 3.0.x lines received no fix on their own branch and are no longer maintained upstream.
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.