vciy

CVE-2026-89060

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Stolostron/multicluster-observability-addon: cross-namespace secret disclosure in multicluster-observability-addon via unvalidated configuration references

CVE-2026-890603 of 4 sources documented this
19

rank 19 = 0 + 19 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00475  ·  without this subject the record ranks 19

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.7, from the CNA  ·  without this subject the record ranks 0

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 19

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 19

Hindsight · the state

0.00475EPSSNOT IN KEVas of 2026-10-18
Severity7.7 HIGHreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix not stated as a versionreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-09-14, 14 days at 0.00, as of 2026-09-28. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Which product do you run? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Choose your product above to watch it.

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-551 Incorrect Behavior Order: Authorization Before Parsing and Canonicalizationreceipt
Published consequencesCWE-551: Access Control: Bypass Protection Mechanismcwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inThe CVE record names a fix, but not as a version that can be installed. What it holds is a source commit, a placeholder, or a version the record itself lists as affected.receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.7 HIGHreceipt
Exploit probability0.00475 · top 60% of all CVEsreceipt
Assigned byredhatreceipt
Recorded changes2 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productRed Hat Advanced Cluster Management for Kubernetes 2.13; Red Hat Advanced Cluster Management for Kubernetes 2.14; Red Hat Advanced Cluster Management for Kubernetes 2.15…receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$14,500over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$14,500 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00475 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Did this affect your environment?Answering needs an account.

Attack path

Network requestrequires low privilegesRed Hat Advanced Cluster Management…CWE-551 weaknessAdjacent componentsscope changeConfidentiality lossC:Hexploits CWE-551scope changedata compromise

What it is stated by the CNA

A cross-namespace authorization flaw in multicluster-observability-addon allows a user with permission to modify a managed cluster’s ManagedClusterAddOn configuration to reference ClusterLogForwarder or OpenTelemetryCollector resources outside the permitted namespace. If those resources reference Secrets, the add-on may copy the referenced Secrets to the attacker-controlled managed cluster. receipt

NVD's analysis a second authority

weakness
CWE-551
also scored by
secalert@redhat.com 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

check it yourself access.redhat.com access.redhat.com access.redhat.com access.redhat.com access.redhat.com access.redhat.com +2 morereceipt

Movement the material steps

14 Sep 20260.00231
28 Sep 20260.00475
Show all 2 observations
14 Sep 20260.00231
28 Sep 20260.00475

2 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00475Published2026-09-11Index as of2026-09-28

The record had been public for 17 days when this index was last written.

Published 2026-09-11 receipt · Index as of 2026-09-28 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2026-89060.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.