FKIE_CVE-2026-45758
Vulnerability from fkie_nvd - Published: 2026-06-05 20:17 - Updated: 2026-07-23 07:10| Vendor | Product | Version | |
|---|---|---|---|
| guardrailsai | guardrails_ai | 0.10.1 |
{
"affected": [
{
"affectedData": [
{
"product": "guardrails",
"vendor": "guardrails-ai",
"versions": [
{
"status": "affected",
"version": "= 0.10.1"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:guardrailsai:guardrails_ai:0.10.1:*:*:*:*:python:*:*",
"matchCriteriaId": "B8011BB6-C398-4C41-87CA-E62DD63CF980",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Guardrails AI is a Python framework that helps build AI applications. On May 11, 2026 at approximately 6:00 PM Pacific, an attacker published a malicious version of `guardrails-ai` (0.10.1) to PyPI. Aany user who installed `guardrails-ai==0.10.1` from PyPI on May 11, 2026 may be affected. Security researchers identified the malicious package within approximately 2 hours of publication, and PyPI quarantined the repository. Based on our telemetry, Guardrails AI maintainers have observed no requests to Guardrails AI infrastructure originating from the malicious 0.10.1 version, and a review of system and access logs has produced no evidence of user data exfiltration through their systems. Users should upgrade to version 0.10.2 or downgrade to version 0.10.0, both of which are unaffected. Those who installed version 0.10.1 should rotate any credentials accessible from their machine (GitHub PATs, cloud provider keys, package registry tokens, API keys) and audit their GitHub account for unauthorized workflows or repositories."
},
{
"lang": "es",
"value": "Guardrails AI es un framework de Python que ayuda a construir aplicaciones de IA. El 11 de mayo de 2026, aproximadamente a las 6:00 PM hora del Pac\u00edfico, un atacante public\u00f3 una versi\u00f3n maliciosa de \u0027guardrails-ai\u0027 (0.10.1) en PyPI. Cualquier usuario que haya instalado \u0027guardrails-ai==0.10.1\u0027 desde PyPI el 11 de mayo de 2026 podr\u00eda verse afectado. Investigadores de seguridad identificaron el paquete malicioso en aproximadamente 2 horas desde su publicaci\u00f3n, y PyPI puso en cuarentena el repositorio. Seg\u00fan nuestra telemetr\u00eda, los mantenedores de Guardrails AI no han observado solicitudes a la infraestructura de Guardrails AI originadas desde la versi\u00f3n maliciosa 0.10.1, y una revisi\u00f3n de los registros de sistema y acceso no ha producido evidencia de exfiltraci\u00f3n de datos de usuario a trav\u00e9s de sus sistemas. Los usuarios deben actualizar a la versi\u00f3n 0.10.2 o degradar a la versi\u00f3n 0.10.0, ambas no afectadas. Aquellos que instalaron la versi\u00f3n 0.10.1 deben rotar cualquier credencial accesible desde su m\u00e1quina (PATs de GitHub, claves de proveedores de la nube, tokens de registro de paquetes, claves de API) y auditar su cuenta de GitHub en busca de flujos de trabajo o repositorios no autorizados."
}
],
"id": "CVE-2026-45758",
"lastModified": "2026-07-23T07:10:00.113",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.6,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 6.0,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-45758",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-06-08T16:20:02.293656Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-06-05T20:17:32.357",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Vendor Advisory"
],
"url": "https://github.com/guardrails-ai/guardrails/blob/main/SECURITY_ADVISORY.md"
},
{
"source": "security-advisories@github.com",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/guardrails-ai/guardrails/issues/1473"
},
{
"source": "security-advisories@github.com",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/guardrails-ai/guardrails/security/advisories/GHSA-xmpw-2vmm-p4p6"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-506"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.