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

Back
New CVE Detected

CVE-2026-73666 – Authentication Bypass – OpenChoreo Backstage Developer Portal (before 1.0.4, 1.1.0–

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-73666 is a missing-authentication vulnerability (CWE-306) in the Backstage-based developer portal component of OpenChoreo, an open-source internal developer platform for Kubernetes. Affected builds shipped with dangerous authentication-bypass flags enabled, exposing the entire developer-portal API without requiring any credentials. The issue carries a CVSS v3.1 base score of 8.2 (High) and is remotely exploitable with no privileges or user interaction required.

Technical details

  • Root cause: The Backstage backend in affected OpenChoreo builds had backend.auth.dangerouslyDisableDefaultAuthPolicy and auth.providers.guest.dangerouslyAllowOutsideDevelopment set to true, which disables Backstage’s default authentication policy and permits guest sign-in outside of development environments.
  • Trigger conditions: No special configuration or attacker preparation is required — any network client that can reach the developer-portal’s /api/* endpoints is treated as authenticated.
  • Attack vector: Network (AV:N) — exploitable by any unauthenticated remote actor with access to the exposed developer-portal endpoint; no privileges (PR:N) or user interaction (UI:N) are needed.
  • Impact: Unauthenticated attackers can read the full OpenChoreo software catalog (including tenant/namespace data), access scaffolder task execution logs, and create or delete catalog locations without authorization — resulting in high confidentiality impact and low integrity impact (no impact to availability).

Affected software

  • OpenChoreo (openchoreo/openchoreo) versions before 1.0.4
  • OpenChoreo versions 1.1.0 through 1.1.3
  • OpenChoreo versions 1.2.0-rc.1 through 1.2.0

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Upgrade OpenChoreo to the patched releases — 1.0.4, 1.1.4, or 1.2.1 — depending on the release line in use.
  • If unable to patch immediately: Explicitly override the two dangerous authentication flags to false in your Helm/configuration values (backend.auth.dangerouslyDisableDefaultAuthPolicy: false and auth.providers.guest.dangerouslyAllowOutsideDevelopment: false) so the Backstage backend enforces its default authentication policy, and restrict network access to the developer-portal API to trusted internal networks until the upgrade is applied.
  • Review developer-portal access logs for unauthenticated /api/* requests and any unexpected catalog location creation/deletion or scaffolder log access that may indicate exploitation.

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