llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · oneuptime

GHSA-8FPH-9J9F-XXGC

Kubernetes AI access test, agent reset and fix approval ignored label and owner scopes on cluster permissions

Sin parche publicado
Descargar PNG JSON
CVSS 3.1
5.4
Media
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición33 dDesde la divulgación, 17 oct 2026, 11:53 p. m.
Detección32 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Monitoreo
Detectada +1
18 oct 26
19 nov 26
20 nov 26
18 oct 26
26 oct 26
3 nov 26
12 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-8FPH-9J9F-XXGC divulgada · CVSS 5.4 (GitHub)
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Summary

A Kubernetes cluster's Test connection (`POST /kubernetes-cluster/ai-access/test`) runs `kubectl version` and `kubectl auth can-i --list` on the cluster through its Kubernetes AI agent or the Runner bound to it, and records the cluster's last verified time. It is meant for people who may edit that cluster, but it only checked whether the caller held a permission to edit clusters anywhere in the project. A permission limited to some labels or to owned clusters, and a block on one of the cluster's labels, were not applied to the cluster being tested, so a member whose edit permission covers only other clusters (for example only clusters labelled Staging) could run the test on any cluster they could view.

The same project-wide check decided related actions. Reset agent on a cluster or on an infrastructure resource (Docker and Podman hosts, Docker Swarm, Proxmox, VMware and Ceph clusters, database servers, hosts) asked for the AI admin permissions and a read of the record, but not for an edit of it. Approving an AI-proposed plan with kubectl commands asked for permission to start runbooks, but not for an edit of each cluster the plan changes. And the AI conversation on an incident or alert offered read-only kubectl and infrastructure commands on every linked cluster and resource with AI investigation on, whoever asked, including people who may not view that cluster or resource.

Impact

An authenticated project member whose permission to edit Kubernetes clusters is limited to other labels or to owned clusters, or blocked for a label the cluster carries, could:

  • run the access test on the cluster: learn its Kubernetes version and the RBAC permissions held by its AI agent or Runner credential, use the agent's time, and update the cluster's last verified time;
  • if they also hold the AI admin permissions (Project Owner, Project Admin or Edit Auto Remediation Rule), reset the cluster's or a resource's AI agent, which disconnects it until it registers again a few minutes later;
  • if they may start runbooks, approve a pending AI-composed kubectl plan for the cluster, so that changes the cluster's own AI settings allow run on a cluster they may not edit.

A responder who could see an incident or alert, but not a cluster or resource linked to it, could have OneUptime AI run read-only kubectl or infrastructure commands on that cluster or resource. Members whose permissions cover every cluster in the project were not affected, and nothing outside the member's own project was reachable.

Patches

Each of these actions now decides the caller's access for that very cluster or resource, as an update of it through the API is decided: labels, owners, blocks, custom roles and read-only credentials included. Test connection, Reset agent and approving a kubectl plan take permission to edit that cluster or resource (Reset agent still also takes the AI admin permissions). The incident's AI conversation offers commands only on the linked clusters and resources the person asking may view.

Fixed in OneUptime 14.0.69 https://github.com/OneUptime/oneuptime/releases/tag/14.0.69. Upgrade to 14.0.69 or later.

Affected versions: `>= 14.0.2, <= 14.0.68`.

Fix: #4960 https://github.com/OneUptime/oneuptime/pull/4960, merged as 264e1ba13149 https://github.com/OneUptime/oneuptime/commit/264e1ba13149cbd4c80cb22f2177b405886b0452.

Workarounds

A member with no permission to edit Kubernetes clusters could not run the access test. Until you upgrade, give members whose cluster access is meant to be limited by labels or ownership no permission to edit clusters, keep the AI admin permissions and the permission to start runbooks to people who may edit every cluster, and turn AI investigation off on clusters and resources that some readers of their incidents may not view.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
oneuptime≥ 14.0.2 ≤ 14.0.68
4.0.69
14.0.2
14.0.68
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmoneuptime
Sin parche — — 4.0.69 no afectada
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/OneUptime/oneuptime/security/advisories/GHSA-8fph-9j9f-xxgc

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.