CVE-2025-66508

The server trusts all reverse-proxy headers by default, so any remote client can spoof X-Forwarded-For to bypass IP-based protections (AllowIPs, API IP whitelist, “localhost-only” checks). All IP-based access control becomes ineffective.

Details

• Gin is created with defaults (gin.Default()), which sets TrustedProxies = 0.0.0.0/0 and uses X-Forwarded-For/X-Real-IP to compute ClientIP().

• IP-based controls rely on ClientIP():

  • AllowIPs / BindDomain (core/middleware/ip_limit.go, core/utils/security/security.go).
  • API IP whitelist (core/middleware/api_auth.go).
  • "localhost-only" checks that depend on ClientIP().

• Because no trusted-proxy range is enforced, any client can send X-Forwarded-For: 127.0.0.1 (or a whitelisted IP) and be treated as coming from that address.

All IP-based access control is rendered ineffective: remote clients can masquerade as localhost or any whitelisted IP, defeating AllowIPs, API IP whitelists, and “localhost-only” protections.

CVE-2025-66508 has a CVSS score of 6.5 (Medium). 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 (2.0.14, 0.0.0-20251201063338-94f7d78cc976); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-66508? CVE-2025-66508 is a medium-severity security vulnerability in github.com/1Panel-dev/1Panel (go), affecting versions < 2.0.14. It is fixed in 2.0.14, 0.0.0-20251201063338-94f7d78cc976.
2. How severe is CVE-2025-66508? CVE-2025-66508 has a CVSS score of 6.5 (Medium). 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-2025-66508?
   • github.com/1Panel-dev/1Panel (go) (versions < 2.0.14)
   • github.com/1Panel-dev/1Panel/agent (go) (versions < 0.0.0-20251201063338-94f7d78cc976)
4. Is there a fix for CVE-2025-66508? Yes. CVE-2025-66508 is fixed in 2.0.14, 0.0.0-20251201063338-94f7d78cc976. Upgrade to this version or later.
5. Is CVE-2025-66508 exploitable, and should I be worried? Whether CVE-2025-66508 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-2025-66508 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-2025-66508?
   • Upgrade github.com/1Panel-dev/1Panel to 2.0.14 or later
   • Upgrade github.com/1Panel-dev/1Panel/agent to 0.0.0-20251201063338-94f7d78cc976 or later