high
7.5
CWE
1286
Advisory Published
Advisory Published
Updated

CVE-2025-22868: Unexpected memory consumption during token parsing in golang.org/x/oauth2

First published: Wed Feb 26 2025(Updated: )

### Summary We have encountered a security vulnerability being reported by our scanners for Traefik 2.11.22. - https://security.snyk.io/vuln/SNYK-CHAINGUARDLATEST-TRAEFIK33-9403297 ### Details It seems to target oauth2/jws library. ### PoC No steps to replicate this vulnerability ### Impact We have a strict control on security and we always try to stay up-to-date with the fixes received for third-party solutions. ## Patches - https://github.com/traefik/traefik/releases/tag/v2.11.24 - https://github.com/traefik/traefik/releases/tag/v3.3.6 - https://github.com/traefik/traefik/releases/tag/v3.4.0-rc2

Credit: security@golang.org

Affected SoftwareAffected VersionHow to fix
go/github.com/traefik/traefik/v3=3.4.0-rc1
3.4.0-rc2
go/github.com/traefik/traefik/v2<2.11.24
2.11.24
go/github.com/traefik/traefik/v3<3.3.6
3.3.6
Go Jws Go<0.27.0

Remedy

https://go.dev/cl/652155

Remedy

https://go.dev/issue/71490

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2025-22868?

    CVE-2025-22868 has been classified as a medium severity vulnerability due to its potential impact on memory consumption during token parsing.

  • How do I fix CVE-2025-22868?

    To fix CVE-2025-22868, it is recommended to update to the latest version of Google OAuth2 that addresses this vulnerability.

  • What type of attacks can exploit CVE-2025-22868?

    CVE-2025-22868 can be exploited through the use of malicious malformed tokens that can lead to unexpected memory consumption.

  • Which software is affected by CVE-2025-22868?

    CVE-2025-22868 specifically affects Google OAuth2 implementations.

  • What are the potential consequences of CVE-2025-22868?

    The potential consequences of CVE-2025-22868 include application crashes or denial of service due to excessive memory usage.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203