Debian Package Tracker
Register | Log in
Subscribe

golang-gopkg-square-go-jose.v1

Javascript Object Signing and Encryption (JOSE) for Go

Choose email to subscribe with

general
  • source: golang-gopkg-square-go-jose.v1 (main)
  • version: 1.1.2-4
  • maintainer: Debian Go Packaging Team (DMD)
  • uploaders: Peter Colberg [DMD] [DM]
  • arch: all
  • std-ver: 4.6.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 1.1.2-2
  • oldstable: 1.1.2-4
  • stable: 1.1.2-4
  • testing: 1.1.2-4
  • unstable: 1.1.2-4
versioned links
  • 1.1.2-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.1.2-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • golang-gopkg-square-go-jose.v1-dev
action needed
1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:
  • CVE-2026-34986: Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.
Created: 2026-04-07 Last update: 2026-04-07 18:30
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2026-34986: Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.
Created: 2026-04-07 Last update: 2026-04-07 18:30
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2026-34986: Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.
Created: 2026-04-07 Last update: 2026-04-07 18:30
1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:
  • CVE-2026-34986: Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.
Created: 2026-04-07 Last update: 2026-04-07 18:30
1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:
  • CVE-2026-34986: Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.
Created: 2026-04-07 Last update: 2026-04-07 18:30
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.2).
Created: 2024-04-07 Last update: 2026-03-31 15:01
news
[rss feed]
  • [2023-02-12] golang-gopkg-square-go-jose.v1 1.1.2-4 MIGRATED to testing (Debian testing watch)
  • [2023-02-09] Accepted golang-gopkg-square-go-jose.v1 1.1.2-4 (source) into unstable (Shengjing Zhu)
  • [2021-11-01] golang-gopkg-square-go-jose.v1 1.1.2-3.1 MIGRATED to testing (Debian testing watch)
  • [2021-10-29] Accepted golang-gopkg-square-go-jose.v1 1.1.2-3.1 (source) into unstable (Paul Gevers)
  • [2021-08-21] Accepted golang-gopkg-square-go-jose.v1 1.1.2-3 (source all) into unstable (Jelmer Vernooij) (signed by: Jelmer Vernooij)
  • [2018-11-21] golang-gopkg-square-go-jose.v1 1.1.2-2 MIGRATED to testing (Debian testing watch)
  • [2018-11-18] Accepted golang-gopkg-square-go-jose.v1 1.1.2-2 (source) into unstable (Peter Colberg)
  • [2018-11-17] Accepted golang-gopkg-square-go-jose.v1 1.1.2-1 (source) into unstable (Peter Colberg)
  • [2016-11-26] Accepted golang-gopkg-square-go-jose.v1 1.1.0-3~bpo8+1 (source all) into jessie-backports (Peter Colberg)
  • [2016-11-25] golang-gopkg-square-go-jose.v1 1.1.0-3 MIGRATED to testing (Debian testing watch)
  • [2016-11-20] Accepted golang-gopkg-square-go-jose.v1 1.1.0-3 (source) into unstable (Peter Colberg)
  • [2016-11-15] Accepted golang-gopkg-square-go-jose.v1 1.1.0-2 (source) into unstable (Dr. Tobias Quathamer)
  • [2016-11-02] Accepted golang-gopkg-square-go-jose.v1 1.1.0-1~bpo8+1 (source all) into jessie-backports, jessie-backports (Peter Colberg) (signed by: Timothy Potter)
  • [2016-09-29] golang-gopkg-square-go-jose.v1 1.1.0-1 MIGRATED to testing (Debian testing watch)
  • [2016-09-24] Accepted golang-gopkg-square-go-jose.v1 1.1.0-1 (source) into unstable (Peter Colberg)
  • [2016-09-10] golang-gopkg-square-go-jose.v1 1.0.5-1 MIGRATED to testing (Debian testing watch)
  • [2016-09-04] Accepted golang-gopkg-square-go-jose.v1 1.0.5-1 (source) into unstable (Peter Colberg)
  • [2016-08-17] golang-gopkg-square-go-jose.v1 1.0.3-1 MIGRATED to testing (Debian testing watch)
  • [2016-08-12] Accepted golang-gopkg-square-go-jose.v1 1.0.3-1 (source) into unstable (Peter Colberg)
  • [2016-05-19] Accepted golang-gopkg-square-go-jose.v1 1.0.2-1 (source all) into unstable, unstable (Peter Colberg) (signed by: Mattia Rizzolo)
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 1.1.2-4

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing