Security readout for executives and security teams
Plain-English summary
CVE-2026-23990 affects Flux Operator Web UI deployments using certain OIDC configurations. If identity claims resolve to empty username and groups, Kubernetes impersonation is skipped and requests may run with the operator service account instead of the user’s limited permissions. This can expose data or elevate access inside affected clusters.
Executive priority
Prioritize remediation for clusters where Flux Operator Web UI is exposed to users and connected to OIDC. The issue is not known to be exploited, but privilege escalation to the operator service account can undermine Kubernetes access controls.
Technical view
Flux Operator versions 0.36.0 through before 0.40.0 fail to validate non-empty username and groups after OIDC claims are processed through CEL expressions. When both are empty, Kubernetes client-go omits impersonation headers, so Web UI API requests execute using the flux-operator service account. The issue is classified as CWE-269 and CWE-862; CVSS 3.1 score is 5.3.
Likely exposure
Exposure is limited to Flux Operator Web UI deployments on versions >=0.36.0 and <0.40.0 with OIDC providers missing expected claims, or custom CEL expressions that can evaluate username and groups to empty values.
Exploitation context
Sources do not report active exploitation, and this CVE is not listed as KEV. Exploitation requires authenticated access and a vulnerable OIDC/CEL claim-mapping condition, but may lead to high-impact confidentiality exposure through operator service account privileges.
Researcher notes
Key condition is empty post-CEL username and groups causing client-go to omit impersonation headers. Focus validation on affected versions, Web UI OIDC use, claim availability, CEL mappings, and the effective permissions of the flux-operator service account. Avoid assuming exposure where Web UI or OIDC is not configured.
Mitigation direction
- Upgrade Flux Operator to version 0.40.0 or later.
- Review vendor advisory and release notes before deployment.
- Ensure OIDC tokens provide expected email and groups claims.
- Review custom CEL expressions for possible empty username or groups outputs.
Validation and detection
- Inventory Flux Operator versions across Kubernetes clusters.
- Identify clusters using the Flux Operator Web UI with OIDC enabled.
- Review OIDC claim mappings and custom CEL expressions for empty results.
- Confirm version 0.40.0 or later is deployed after remediation.
- Check audit logs for Web UI requests lacking expected user impersonation context.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23990 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N1.63.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/controlplaneio-fluxcd/flux-operator/security/advisories/GHSA-4xh5-jcj2-ch8qCVE reference · x_refsource_CONFIRM
- https://github.com/controlplaneio-fluxcd/flux-operator/pull/610CVE reference · x_refsource_MISC
- https://github.com/controlplaneio-fluxcd/flux-operator/commit/084540424f6de8ba5d88fb1fd1e8472ba29afd7eCVE reference · x_refsource_MISC
- https://github.com/controlplaneio-fluxcd/flux-operator/releases/tag/v0.40.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.