Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2024-51744

Published

golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.

Source published
4 Nov 2024 21:47:12 UTC
Source modified
5 Nov 2024 16:11:42 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

euvd · EUVD-2024-3178

Published

golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 4, 2024, 9:47:12 PM

dateUpdated: Nov 5, 2024, 4:11:42 PM

31 related source bulletins · separate from aliases

openSUSE-SU-2026:12300-1: kumactl-3.0.0-1.1 on GA media

CVE-2024-45337 · CVE-2024-45338 · CVE-2024-51744 · CVE-2025-22869 · CVE-2025-22872 · CVE-2025-30204 · CVE-2025-47911 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-58181 · CVE-2025-58190 · CVE-2026-26958 · CVE-2026-33186 · CVE-2026-41178

SUSE-SU-2025:0546-1: Security update golang-github-prometheus-prometheus

CVE-2024-51744

openSUSE-SU-2024:14495-1: rclone-1.68.1-2.1 on GA media

CVE-2024-51744

RHSA-2025:11351: Red Hat Security Advisory: OpenShift Container Platform 4.15.55 bug fix and security update

CVE-2024-51744 · CVE-2025-22868

openSUSE-SU-2026:20654-1: Security update for grafana

CVE-2023-45288 · CVE-2024-11741 · CVE-2024-28180 · CVE-2024-45339 · CVE-2024-51744 · CVE-2024-9264 · CVE-2024-9476 · CVE-2025-11065 · CVE-2025-21613 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-2703 · CVE-2025-27144 · CVE-2025-29923 · CVE-2025-3415 · CVE-2025-3454 · CVE-2025-3580 · CVE-2025-4123 · CVE-2025-47911 · CVE-2025-58190 · CVE-2025-6023 · CVE-2025-6197 · CVE-2025-64751 · CVE-2025-68156 · CVE-2026-21720 · CVE-2026-21721 · CVE-2026-21722

openSUSE-SU-2025:20117-1: Security update for trivy

CVE-2024-3817 · CVE-2024-45337 · CVE-2024-45338 · CVE-2024-51744 · CVE-2025-11065 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22872 · CVE-2025-27144 · CVE-2025-30204 · CVE-2025-46569 · CVE-2025-47291 · CVE-2025-53547 · CVE-2025-58058

SUSE-SU-2025:0524-1: Security update for SUSE Manager Client Tools

CVE-2023-3128 · CVE-2023-6152 · CVE-2024-22037 · CVE-2024-45337 · CVE-2024-51744 · CVE-2024-6837 · CVE-2024-8118

openSUSE-SU-2025:14988-1: cosign-2.5.0-1.1 on GA media

CVE-2024-51744 · CVE-2024-6104 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-27144

SUSE-SU-2025:01985-1: Security update 4.3.15 for Multi-Linux Manager Server

CVE-2023-45288 · CVE-2024-11741 · CVE-2024-45337 · CVE-2024-45339 · CVE-2024-47535 · CVE-2024-51744 · CVE-2024-9264 · CVE-2024-9476 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-2703 · CVE-2025-27144 · CVE-2025-3454 · CVE-2025-3580 · CVE-2025-4123

openSUSE-SU-2024:14517-1: traefik2-2.11.14-1.1 on GA media

CVE-2024-51744

SUSE-SU-2024:4042-1: Security update for govulncheck-vulndb

CVE-2024-10389 · CVE-2024-10975 · CVE-2024-45794 · CVE-2024-48057 · CVE-2024-51735 · CVE-2024-51744 · CVE-2024-51746

openSUSE-SU-2024:14522-1: traefik-3.2.1-1.1 on GA media

CVE-2024-51744

openSUSE-SU-2026:20798-1: Security update for trivy

CVE-2024-3817 · CVE-2024-45337 · CVE-2024-45338 · CVE-2024-51744 · CVE-2025-11065 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22872 · CVE-2025-27144 · CVE-2025-30204 · CVE-2025-46569 · CVE-2025-47291 · CVE-2025-47911 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-53547 · CVE-2025-58058 · CVE-2025-58181 · CVE-2025-58190

openSUSE-SU-2024:14484-1: govulncheck-vulndb-0.0.20241112T145010-1.1 on GA media

CVE-2024-51744

openSUSE-SU-2025-20117-1: Security update for trivy

CVE-2024-3817 · CVE-2024-45337 · CVE-2024-45338 · CVE-2024-51744 · CVE-2025-11065 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22872 · CVE-2025-27144 · CVE-2025-30204 · CVE-2025-46569 · CVE-2025-47291 · CVE-2025-53547 · CVE-2025-58058

SUSE-SU-2025:1333-1: Security update for cosign

CVE-2024-51744 · CVE-2024-6104 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-27144

openSUSE-SU-2026:12297-1: kubectl-retina-1.3.1-1.1 on GA media

CVE-2024-51744 · CVE-2025-22872 · CVE-2025-27144 · CVE-2025-30204 · CVE-2025-54410 · CVE-2025-58190 · CVE-2026-33186 · CVE-2026-34986 · CVE-2026-53941 · CVE-2026-72815 · CVE-2026-95838

RHSA-2026:2737: Red Hat Security Advisory: Red Hat Ceph Storage

CVE-2019-10790 · CVE-2021-23358 · CVE-2022-34749 · CVE-2024-31884 · CVE-2024-51744 · CVE-2024-55565 · CVE-2025-6176 · CVE-2025-7783 · CVE-2025-12816 · CVE-2025-14104 · CVE-2025-26791 · CVE-2025-47907 · CVE-2025-47913 · CVE-2025-58183 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-68429

openSUSE-SU-2025:0131-1: Security update for coredns

CVE-2024-51744

msrc_CVE-2024-51744: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt

CVE-2024-51744

openSUSE-SU-2026:20099-1: Security update for coredns

CVE-2024-51744 · CVE-2025-58063 · CVE-2025-68156 · CVE-2025-68161

openSUSE-SU-2026:20620-1: Security update for rclone

CVE-2024-45337 · CVE-2024-45338 · CVE-2024-51744 · CVE-2024-52522 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-30204 · CVE-2025-58181 · CVE-2025-68121 · CVE-2026-1229 · CVE-2026-27141 · CVE-2026-33186 · CVE-2026-41176 · CVE-2026-41179

openSUSE-SU-2025:14768-1: grafana-11.5.1-1.1 on GA media

CVE-2024-51744

RHSA-2025:11681: Red Hat Security Advisory: OpenShift Container Platform 4.16.45 bug fix and security update

CVE-2024-45339 · CVE-2024-51744 · CVE-2025-6032 · CVE-2025-30204 · CVE-2025-48060

RHSA-2026:3406: Red Hat Security Advisory: New container image: rhceph-9.0

CVE-2021-23358 · CVE-2024-45310 · CVE-2024-51744 · CVE-2024-55565 · CVE-2025-6176 · CVE-2025-7783 · CVE-2025-14104 · CVE-2025-22868 · CVE-2025-26791 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-66418 · CVE-2025-66471 · CVE-2026-21441

openSUSE-SU-2024:14481-1: coredns-1.11.3+git129.387f34d-1.1 on GA media

CVE-2024-51744

openSUSE-SU-2025:14663-1: velociraptor-0.7.0.4.git142.862ef23-1.1 on GA media

CVE-2023-1732 · CVE-2023-44270 · CVE-2023-45133 · CVE-2023-45683 · CVE-2023-46234 · CVE-2024-21538 · CVE-2024-23331 · CVE-2024-24786 · CVE-2024-28180 · CVE-2024-31207 · CVE-2024-37298 · CVE-2024-4067 · CVE-2024-4068 · CVE-2024-42459 · CVE-2024-42460 · CVE-2024-42461 · CVE-2024-45296 · CVE-2024-45338 · CVE-2024-45811 · CVE-2024-45812 · CVE-2024-47068 · CVE-2024-47875 · CVE-2024-48948 · CVE-2024-48949 · CVE-2024-51744 · CVE-2024-55565 · CVE-2024-6104

openSUSE-SU-2025:14840-1: trivy-0.59.1-1.1 on GA media

CVE-2024-51744 · CVE-2025-27144

RHSA-2026:2769: Red Hat Security Advisory: Red Hat Ceph Storage 7.1 security and bug fix updates

CVE-2021-23358 · CVE-2022-34749 · CVE-2024-11831 · CVE-2024-31884 · CVE-2024-47866 · CVE-2024-51744 · CVE-2024-55565 · CVE-2025-26791 · CVE-2025-47913 · CVE-2025-52555 · CVE-2025-61729

SUSE-SU-2025:0525-1: Security update for SUSE Manager Client Tools

CVE-2023-3128 · CVE-2023-6152 · CVE-2024-22037 · CVE-2024-45337 · CVE-2024-51744 · CVE-2024-6837 · CVE-2024-8118

openSUSE-SU-2026:12270-1: flannel-0.28.10-1.1 on GA media

CVE-2024-51744 · CVE-2026-32241 · CVE-2026-46600 · CVE-2026-56852

Source published
Nov 4, 2024, 9:47:12 PM (timezone not stated)
Source modified
Nov 5, 2024, 4:11:42 PM (timezone not stated)
Saved here
16 Nov 2026 08:34:43 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

nvd · CVE-2024-51744

Published

golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-755

Original publisher date fields

published: 2024-11-04T22:15:03.997

lastModified: 2026-06-17T08:06:14.123

Source published
4 Nov 2024 22:15:03 UTC
Source modified
17 Jun 2026 08:06:14 UTC
Saved here
25 Oct 2026 01:17:12 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

osv · GHSA-29wx-vh33-7x7r

Published

### Summary Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. ### Fix We have back-ported the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. ### Workaround We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above. ```Go token, err := /* jwt.Parse or similar */ if token.Valid { fmt.Println("You look nice today") } else if errors.Is(err, jwt.ErrTokenMalformed) { fmt.Println("That's not even a token") } else if errors.Is(err, jwt.ErrTokenUnverifiable) { fmt.Println("We could not verify this token") } else if errors.Is(err, jwt.ErrTokenSignatureInvalid) { fmt.Println("This token has an invalid signature") } else if errors.Is(err, jwt.ErrTokenExpired) || errors.Is(err, jwt.ErrTokenNotValidYet) { // Token is either expired or not active yet fmt.Println("Timing is everything") } else { fmt.Println("Couldn't handle this token:", err) } ```

Source published
4 Nov 2024 23:22:41 UTC
Source modified
10 Sep 2026 03:50:20 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Publisher rating · LOW

osv · GO-2024-3250

Published

Improper error handling in ParseWithClaims and bad documentation may cause dangerous situations in github.com/golang-jwt/jwt

Source published
12 Nov 2024 13:55:08 UTC
Source modified
4 Feb 2026 02:44:04 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 12:50 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current