Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-65956 – Missing Authentication / SSRF via SSO Config Endpoints – KubePi ≤ 1.6.15

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-65956 is a missing-authentication vulnerability (CWE-306) in KubePi, a Kubernetes multi-cluster management panel maintained by 1Panel-dev. SSO/OIDC/SAML configuration management endpoints share the same public routing boundary as the SSO login and callback endpoints, allowing unauthenticated or low-privileged users to read and modify global authentication settings. The issue carries a CVSS score of 10.0 (Critical) and can lead to account takeover, privilege escalation, and server-side request forgery (SSRF).

Technical details

  • Root cause: SSO management routes (configuration create/read/update) were placed on the same publicly-reachable routing boundary as the SSO login/callback routes, so no administrator authorization check was enforced on the management operations.
  • Trigger conditions: An attacker sends unauthenticated requests directly to the exposed SSO/OIDC/SAML configuration API endpoints on an internet-facing KubePi instance.
  • Attack vector: Network, no privileges or user interaction required.
  • Impact: Unauthorized viewing/modification of global SSO configuration can enable account takeover or privilege escalation; the SSO "connectivity test" function can be abused as an SSRF primitive; the user-list API additionally returned authentication-related fields without properly redacting them.

Affected software

  • KubePi (1Panel-dev) versions up to and including 1.6.15
  • Fixed in version 2.0.0

Severity

  • CVSS v4.0 Base Score: 10.0 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Mitigation and recommended actions

  • Immediate: Upgrade KubePi to version 2.0.0 or later, which restricts SSO configuration operations to authenticated administrators, limits public access to only login/callback/status/SAML endpoints, removes sensitive authentication fields from user-list responses, and adds a minimal public endpoint for auth-type retrieval.
  • If immediate patching is not possible: Restrict network access to KubePi’s management interface (e.g., place it behind a VPN or IP allowlist) and disable or avoid configuring SSO/OIDC/SAML until the upgrade can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge