CVE-2026-48089
DevGuard has improper authorization on public assets
Description
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 — including users from a different organization with no membership or role in the affected org/project — 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.
INFO
Published Date :
June 19, 2026, 8:16 p.m.
Last Modified :
Oct. 25, 2026, 11:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 4.0 | HIGH | [email protected] |
Solution
- Update DevGuard to version 1.4.2 or later.
- As a workaround, make affected assets non-public.
- Grant explicit access to downstream consumers if needed.
- Export files for downstream consumers if necessary.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-48089.
| URL | Resource |
|---|---|
| https://github.com/l3montree-dev/devguard/commit/1be88ec1309a5dc0566e35a23bdc4ea3ecd11417 | |
| https://github.com/l3montree-dev/devguard/security/advisories/GHSA-6p54-fw2f-q7gf |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-48089 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-48089
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-48089 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-48089 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 25, 2026
Action Type Old Value New Value Added Translation Title: devguard de l3montree-dev, Description: DevGuard proporciona gestión de vulnerabilidades para toda la cadena de suministro de software. Antes de la versión 1.4.2, en una instancia de API de DevGuard con uno o más activos públicos, cualquier usuario autenticado -incluidos los usuarios de una organización diferente sin membresía ni rol en la organización/proyecto afectado- puede crear, actualizar, reaplicar y eliminar reglas VEX en esos activos públicos. La misma falla afecta a los otros puntos finales de escritura de triaje de vulnerabilidades expuestos bajo un activo público, incluyendo la creación / actualización / reaplicación / eliminación de reglas VEX; la creación de eventos de vulnerabilidad de dependencia (decisiones de aceptar / rechazar / mitigar), la creación de eventos por lotes, la sincronización de vulnerabilidades y la mitigación; la creación de riesgo de licencia; las escrituras de referencias externas; y/o la creación de artefactos y la actualización de licencias. El atacante necesita una cuenta válida en la instancia, pero no se requiere membresía en la organización, proyecto o activo víctima. La versión ’v1.4.2’ contiene un parche. Como solución alternativa, haga que los activos afectados no sean públicos. En la configuración del activo, cambie la visibilidad de pública a privada. Esto elimina la exención de lectura pública en el middleware de control de acceso y restaura la autorización correcta en todos los puntos finales de escritura para ese activo. Los consumidores descendentes que previamente dependían de los puntos finales públicos ’vex.json’ / ’sbom.json’ deberán recibir acceso explícito o deben recibir una versión de archivo exportada hasta que se implemente la versión parcheada. -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 22, 2026
Action Type Old Value New Value Added SSVC {'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'} -
New CVE Received by [email protected]
Jun. 19, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'l3montree-dev', 'product': 'devguard', 'versions': [{'status': 'affected', 'version': '< 1.4.2'}]}] Added Description 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 — including users from a different organization with no membership or role in the affected org/project — 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. Added CVSS V4.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 Added CWE CWE-285 Added CWE CWE-863 Added Reference https://github.com/l3montree-dev/devguard/commit/1be88ec1309a5dc0566e35a23bdc4ea3ecd11417 Added Reference https://github.com/l3montree-dev/devguard/security/advisories/GHSA-6p54-fw2f-q7gf