CVE-2026-48089

{"id": "CVE-2026-48089", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-48089", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-22T17:17:04.632906Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.1, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/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": "PRESENT", "privilegesRequired": "LOW", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "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": "l3montree-dev", "product": "devguard", "versions": [{"status": "affected", "version": "< 1.4.2"}]}]}], "published": "2026-06-19T20:16:16.583", "references": [{"url": "https://github.com/l3montree-dev/devguard/commit/1be88ec1309a5dc0566e35a23bdc4ea3ecd11417", "source": "security-advisories@github.com"}, {"url": "https://github.com/l3montree-dev/devguard/security/advisories/GHSA-6p54-fw2f-q7gf", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-285"}, {"lang": "en", "value": "CWE-863"}]}], "descriptions": [{"lang": "en", "value": "DevGuard provides vulnerability management for the full software supply chain. Prior to 1.4.2, on a DevGuard API instance with one or more public assets, any authenticated user \u2014 including users from a different organization with no membership or role in the affected org/project \u2014 can create, update, reapply, and delete VEX rules on those public assets. The same flaw affects the other vulnerability-triage write endpoints exposed under a public asset, including VEX rule create / update / reapply / delete; dependency-vuln event creation (accept / reject / mitigate decisions), batch event creation, vuln sync, and mitigation; license risk creation; external reference writes; and/or artifact creation and license refresh. The attacker needs a valid account on the instance, but no membership in the victim organization, project, or asset is required. Version `v1.4.2`contains a patch. As a workaround, make affected assets non-public. In the asset settings, switch visibility from public to private. This removes the public-read exemption in the access-control middleware and restores correct authorization on all write endpoints for that asset. Downstream consumers that previously relied on the public `vex.json` / `sbom.json` endpoints will need to be granted explicit access or must receive an exported file version until the patched release is deployed."}, {"lang": "es", "value": "DevGuard proporciona gesti\u00f3n de vulnerabilidades para toda la cadena de suministro de software. Antes de la versi\u00f3n 1.4.2, en una instancia de API de DevGuard con uno o m\u00e1s activos p\u00fablicos, cualquier usuario autenticado -incluidos los usuarios de una organizaci\u00f3n diferente sin membres\u00eda ni rol en la organizaci\u00f3n/proyecto afectado- puede crear, actualizar, reaplicar y eliminar reglas VEX en esos activos p\u00fablicos. La misma falla afecta a los otros puntos finales de escritura de triaje de vulnerabilidades expuestos bajo un activo p\u00fablico, incluyendo la creaci\u00f3n / actualizaci\u00f3n / reaplicaci\u00f3n / eliminaci\u00f3n de reglas VEX; la creaci\u00f3n de eventos de vulnerabilidad de dependencia (decisiones de aceptar / rechazar / mitigar), la creaci\u00f3n de eventos por lotes, la sincronizaci\u00f3n de vulnerabilidades y la mitigaci\u00f3n; la creaci\u00f3n de riesgo de licencia; las escrituras de referencias externas; y/o la creaci\u00f3n de artefactos y la actualizaci\u00f3n de licencias. El atacante necesita una cuenta v\u00e1lida en la instancia, pero no se requiere membres\u00eda en la organizaci\u00f3n, proyecto o activo v\u00edctima. La versi\u00f3n \u2019v1.4.2\u2019 contiene un parche. Como soluci\u00f3n alternativa, haga que los activos afectados no sean p\u00fablicos. En la configuraci\u00f3n del activo, cambie la visibilidad de p\u00fablica a privada. Esto elimina la exenci\u00f3n de lectura p\u00fablica en el middleware de control de acceso y restaura la autorizaci\u00f3n correcta en todos los puntos finales de escritura para ese activo. Los consumidores descendentes que previamente depend\u00edan de los puntos finales p\u00fablicos \u2019vex.json\u2019 / \u2019sbom.json\u2019 deber\u00e1n recibir acceso expl\u00edcito o deben recibir una versi\u00f3n de archivo exportada hasta que se implemente la versi\u00f3n parcheada."}], "lastModified": "2026-10-25T23:10:00.167", "sourceIdentifier": "security-advisories@github.com"}