CVE-2025-68476

{"id": "CVE-2025-68476", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-68476", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-12-22T21:55:53.031327Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.2, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "HIGH", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "kedacore", "product": "keda", "versions": [{"status": "affected", "version": "< 2.17.3"}, {"status": "affected", "version": ">= 2.18.0, < 2.18.3"}]}]}], "published": "2025-12-22T22:16:09.307", "references": [{"url": "https://github.com/kedacore/keda/commit/15c5677f65f809b9b6b59a52f4cf793db0a510fd", "source": "security-advisories@github.com"}, {"url": "https://github.com/kedacore/keda/security/advisories/GHSA-c4p6-qg4m-9jmr", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-22"}, {"lang": "en", "value": "CWE-863"}]}], "descriptions": [{"lang": "en", "value": "KEDA is a Kubernetes-based Event Driven Autoscaling component. Prior to versions 2.17.3 and 2.18.3, an Arbitrary File Read vulnerability has been identified in KEDA, potentially affecting any KEDA resource that uses TriggerAuthentication to configure HashiCorp Vault authentication. The vulnerability stems from an incorrect or insufficient path validation when loading the Service Account Token specified in spec.hashiCorpVault.credential.serviceAccount. An attacker with permissions to create or modify a TriggerAuthentication resource can exfiltrate the content of any file from the node's filesystem (where the KEDA pod resides) by directing the file's content to a server under their control, as part of the Vault authentication request. The potential impact includes the exfiltration of sensitive system information, such as secrets, keys, or the content of files like /etc/passwd. This issue has been patched in versions 2.17.3 and 2.18.3."}, {"lang": "es", "value": "KEDA es un componente de autoescalado basado en eventos para Kubernetes. Versiones anteriores a las 2.17.3 y 2.18.3, se ha identificado una vulnerabilidad de lectura arbitraria de archivos en KEDA, que podr\u00eda afectar a cualquier recurso de KEDA que utilice TriggerAuthentication para configurar la autenticaci\u00f3n de HashiCorp Vault. La vulnerabilidad se origina en una validaci\u00f3n de ruta incorrecta o insuficiente al cargar el Token de Cuenta de Servicio especificado en spec.hashiCorpVault.credential.serviceAccount. Un atacante con permisos para crear o modificar un recurso TriggerAuthentication puede exfiltrar el contenido de cualquier archivo del sistema de archivos del nodo (donde reside el pod de KEDA) dirigiendo el contenido del archivo a un servidor bajo su control, como parte de la solicitud de autenticaci\u00f3n de Vault. El impacto potencial incluye la exfiltraci\u00f3n de informaci\u00f3n sensible del sistema, como secretos, claves o el contenido de archivos como /etc/p4ssd. Este problema ha sido parcheado en las versiones 2.17.3 y 2.18.3."}], "lastModified": "2026-09-25T23:10:00.463", "sourceIdentifier": "security-advisories@github.com"}