Finding and attribution
With the documented default cluster-wide watch configuration, a namespace tenant able to create a VMAgent can cause the operator to create a ServiceAccount in the tenant namespace and bind it to a cluster-scoped role granting cluster-wide Secret read/list/watch. Because the tenant can mint a token for that namespaced ServiceAccount, it can read Secrets across namespaces and use available secrets or workload permissions to escalate further, potentially to cluster-admin. The tested versions and permissions are preserved in the advisory.
Product: VictoriaMetrics Operator. AI system: Claude Opus 4.7. Team / organization: Anthropic.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): The VictoriaMetrics Operator advisory explicitly credits finder Artem Cherezov with Claude Opus 4.7 and includes a verified reproduction. It does not state the internal discovery date.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The primary maintainer advisory documents public disclosure but does not establish whether defenders knew of the issue or whether it was exploited before disclosure.
Remediation status: fix documented. The advisory lists fixes in operator versions 0.68.7 (LTS) and 0.73.0. Release availability does not establish downstream deployment.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 2 Sep 2026. AI attribution dated 2 Sep 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Critical · highest recorded score 9.9. Documented technical effects: privilege escalation, data disclosure.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- Case-level assessment: CVSS 3.1 · 9.9 (Critical) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. VictoriaMetrics Operator GitHub Security Advisory · checked 16 Nov 2026.
Case-level evidence: privilege escalation, data disclosure.
Prerequisites / affected scope: A tenant with namespace edit permissions and permission to create VMAgent resources can trigger default operator behavior that creates a tenant-namespaced ServiceAccount with cluster-wide Secret read/list/watch. The advisory describes cluster-admin escalation paths via accessible secrets..
Exploitation evidence: The advisory presents a verified test reproduction; it does not report exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: The advisory lists fixes in operator versions 0.68.7 (LTS) and 0.73.0. Release availability does not establish downstream deployment.