jackson-dataformat-cbor - Debian Package Tracker

general

source: jackson-dataformat-cbor (main)
version: 2.7.8-5.1
maintainer: Debian Java Maintainers (archive) (DMD)
arch: all
std-ver: 4.6.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.7.8-3
o-o-sec: 2.7.8-3+deb11u1
oldstable: 2.7.8-5
stable: 2.7.8-5.1
testing: 2.7.8-5.1
unstable: 2.7.8-5.1

versioned links

2.7.8-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.8-3+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.8-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.8-5.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libjackson2-dataformat-cbor

action needed

Problems while searching for a new upstream version high

uscan had problems while searching for a new upstream version:

In debian/watch no matching files for watch source
  https://github.com/FasterXML/jackson-dataformat-cbor/releases

Created: 2025-11-27 Last update: 2026-10-10 03:02

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2025-04-04 Last update: 2026-10-06 04:32

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2026-68495: 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.

Created: 2026-10-01 Last update: 2026-10-02 08:31

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2026-68495: 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.

Created: 2026-10-01 Last update: 2026-10-02 08:31

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2026-68495: 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.

Created: 2026-10-01 Last update: 2026-10-02 08:31

2 security issues in bookworm high

There are 2 open security issues in bookworm.

1 important issue:

CVE-2026-68495: 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.

1 ignored issue:

CVE-2020-28491: This affects the package com.fasterxml.jackson.dataformat:jackson-dataformat-cbor from 0 and before 2.11.4, from 2.12.0-rc1 and before 2.12.1. Unchecked allocation of byte buffer can cause a java.lang.OutOfMemoryError exception.

Created: 2026-10-01 Last update: 2026-10-02 08:31

lintian reports 1 error and 1 warning high

Lintian reports 1 error and 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2020-09-21 Last update: 2025-09-11 09:03

2 open merge requests in Salsa normal

There are 2 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2026-09-30 Last update: 2026-09-30 23:01

debian/patches: 2 patches to forward upstream low

Among the 2 debian patches available in version 2.7.8-5.1 of the package, we noticed the following issues:

2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2025-04-04 21:33

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.6.0).

Created: 2022-05-11 Last update: 2026-03-31 15:01

news

[rss feed]

[2026-06-08] Accepted jackson-dataformat-cbor 2.7.8-3+deb11u1 (source) into oldoldstable-security (Markus Koschany)
[2025-04-09] jackson-dataformat-cbor 2.7.8-5.1 MIGRATED to testing (Debian testing watch)
[2025-04-04] Accepted jackson-dataformat-cbor 2.7.8-5.1 (source) into unstable (Bastian Germann) (signed by: bage@debian.org)
[2021-11-09] jackson-dataformat-cbor 2.7.8-5 MIGRATED to testing (Debian testing watch)
[2021-11-04] Accepted jackson-dataformat-cbor 2.7.8-5 (source) into unstable (Markus Koschany)
[2021-11-02] Accepted jackson-dataformat-cbor 2.7.8-4 (source) into unstable (Markus Koschany)
[2018-02-01] jackson-dataformat-cbor 2.7.8-3 MIGRATED to testing (Debian testing watch)
[2018-01-26] Accepted jackson-dataformat-cbor 2.7.8-3 (source) into unstable (Markus Koschany)
[2017-10-19] jackson-dataformat-cbor 2.7.8-2 MIGRATED to testing (Debian testing watch)
[2017-10-13] Accepted jackson-dataformat-cbor 2.7.8-2 (source) into unstable (Markus Koschany)
[2016-12-31] jackson-dataformat-cbor 2.7.8-1 MIGRATED to testing (Debian testing watch)
[2016-12-19] Accepted jackson-dataformat-cbor 2.7.8-1 (source all) into unstable (Emmanuel Bourg)
[2016-04-18] jackson-dataformat-cbor 2.7.3-1 MIGRATED to testing (Debian testing watch)
[2016-04-11] Accepted jackson-dataformat-cbor 2.7.3-1 (source all) into unstable (Emmanuel Bourg)
[2014-10-24] jackson-dataformat-cbor 2.4.3-1 MIGRATED to testing (Britney)
[2014-10-13] Accepted jackson-dataformat-cbor 2.4.3-1 (source all) into unstable, unstable (Hilko Bengen)

bugs [bug history graph]

all: 2
RC: 0
I&N: 0
M&W: 2
F&P: 0
patch: 0

links

homepage
lintian (1, 1)
buildd: logs, reproducibility
popcon
browse source code
other distros
security tracker
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.7.8-5.1