GHSA-6p54-fw2f-q7gf
Suggest an improvement- Source
- https://github.com/advisories/GHSA-6p54-fw2f-q7gf
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/06/GHSA-6p54-fw2f-q7gf/GHSA-6p54-fw2f-q7gf.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-6p54-fw2f-q7gf
- Aliases
- Published
- 2026-06-11T20:26:18Z
- Modified
- 2026-07-15T22:00:51Z
- Severity
-
- 7.1 (High) CVSS_V4 - 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 CVSS Calculator
- Summary
- DevGuard has improper authorization on public assets
- Details
-
Impact
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
- 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.
Security impact is primarily to integrity of the vulnerability picture of public assets: an attacker can mark CVEs as false-positive, silence vulnerabilities, attach misleading justifications, or delete legitimate triage rules — undermining the trustworthiness of every consumer of the affected asset's VEX/SBOM output. Because public assets are by definition consumed by third parties (downstream users, supply-chain consumers, the published vex.json/sbom.json), the blast radius extends to anyone relying on that data.
Private assets are not affected by this advisory: the public-read exemption that enables the bypass does not apply to them, and access remains correctly gated by organization/project membership. The private setting is only relevant in DevGuard itself — there is no impact given when you have an open-source project on e.g. GitLab/GitHub and a private DevGuard asset connected.
Patches
Version
v1.4.2contains a patch. Users should upgrade to the patched release as soon as it is available.Workarounds
If developers cannot upgrade their applications immediately:
- ** They should 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.jsonendpoints will need to be granted explicit access or must receive an exported file version until the patched release is deployed.
Resources
Fixed commit: https://github.com/l3montree-dev/devguard/commit/1be88ec1309a5dc0566e35a23bdc4ea3ecd11417
Credit
DeevGuard thanks @philipflohr (awesome-it.de) for finding and responsibly reporting this vulnerability!
- Database specific
{ "cwe_ids": [ "CWE-285", "CWE-863" ], "github_reviewed": true, "github_reviewed_at": "2026-06-11T20:26:18Z", "nvd_published_at": "2026-06-19T20:16:16Z", "severity": "HIGH" }- References
Affected packages
Go / github.com/l3montree-dev/devguard
Package
- Name
- github.com/l3montree-dev/devguard
- View open source insights on deps.dev
- Purl
- pkg:golang/github.com/l3montree-dev/devguard