CVE-2019-25211

Gin mishandles a wildcard at the end of an origin string

parseWildcardRules in Gin-Gonic CORS middleware before 1.6.0 mishandles a wildcard at the end of an origin string, e.g., https://example.community/* is allowed when the intention is that only https://example.com/* should be allowed, and http://localhost.example.com/* is allowed when the intention is that only http://localhost/* should be allowed.

CVE-2019-25211 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2019-25211? CVE-2019-25211 is a critical-severity security vulnerability in github.com/gin-gonic/gin (go), affecting versions < 1.6.0. It is fixed in 1.6.0.
2. How severe is CVE-2019-25211? CVE-2019-25211 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2019-25211?
   • github.com/gin-gonic/gin (go) (versions < 1.6.0)
   • github.com/gin-contrib/cors (go) (versions < 1.6.0)
4. Is there a fix for CVE-2019-25211? Yes. CVE-2019-25211 is fixed in 1.6.0. Upgrade to this version or later.
5. Is CVE-2019-25211 exploitable, and should I be worried? Whether CVE-2019-25211 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2019-25211 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2019-25211?
   • Upgrade github.com/gin-gonic/gin to 1.6.0 or later
   • Upgrade github.com/gin-contrib/cors to 1.6.0 or later

Other vulnerabilities in github.com/gin-gonic/gin