CVE-2026-48089: Github.com/l3montree dev/devguard DevGuard Has Improper Authorization On Vulnerability

HIGH
Advisory Identifier: GHSA-6p54-fw2f-q7gf
CWE-285 CWE-863
Published
Advisory Summary

CVE-2026-48089 is a HIGH devguard has improper authorization on vulnerability (CWE-285: Improper Authorization) affecting Github.com/l3montree dev/devguard libraries in the Go ecosystem. The issue involves devguard has improper authorization on public assets. Remediation is available by upgrading affected packages to version 1.4.2.

CVE-2026-48089 at a Glance

CVE Identifier CVE-2026-48089
GHSA Identifier GHSA-6p54-fw2f-q7gf
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-285: Improper Authorization
Affected Product Github.com/l3montree dev/devguard
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-48089

To remediate this vulnerability, upgrade all affected Github.com/l3montree dev/devguard dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/l3montree-dev/devguard fixed: 1.4.2
Upgrade github.com/l3montree-dev/devguard to 1.4.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/l3montree-dev/devguard

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-48089, inspect your project dependencies for Github.com/l3montree dev/devguard:

inspect dependencies for github.com/l3montree-dev/devguard

Analyze the terminal output to locate any version of Github.com/l3montree dev/devguard in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.4.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Github.com/l3montree dev/devguard, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.2`contains 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.json` endpoints 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](https://awesome-it.de/)) for finding and responsibly reporting this vulnerability!

CVE-2026-48089 Affected Github.com/l3montree dev/devguard Versions

1 component(s)
Fixed Versions:
1.4.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/l3montree-dev/devguard
Go
< 1.4.2
1.4.2

References

Frequently Asked Questions

What is CVE-2026-48089?
CVE-2026-48089 is a security vulnerability in Github.com/l3montree dev/devguard involving DevGuard has improper authorization on public assets under CWE-285: Improper Authorization.
Which Github.com/l3montree dev/devguard versions are affected?
Affected versions include releases prior to 1.4.2 across affected packages: github.com/l3montree-dev/devguard.
What version fixes CVE-2026-48089?
Upgrading to 1.4.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/l3montree-dev/devguard affected?
Yes, github.com/l3montree-dev/devguard is affected in releases prior to 1.4.2. Upgrade your dependency to 1.4.2 or later.
What CWE is associated with CVE-2026-48089?
CVE-2026-48089 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for CVE-2026-48089?
Run the dependency tree command: 'inspect dependencies for github.com/l3montree-dev/devguard'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6p54-fw2f-q7gf",
  "modified" : "2026-07-15T21:58:25Z",
  "published" : "2026-06-11T20:26:18Z",
  "aliases" : [ "CVE-2026-48089" ],
  "summary" : "DevGuard has improper authorization on public assets",
  "details" : "### Impact\n\nOn 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:\n\n- VEX rule create / update / reapply / delete\n- Dependency-vuln event creation (accept / reject / mitigate decisions), batch event creation, vuln sync, and mitigation\n- License risk creation\n- External reference writes\n- Artifact creation and license refresh\n\nThe attacker needs a valid account on the instance, but no membership in the victim organization, project, or asset is required.\n\n**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.\n\nPrivate 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.\n\n### Patches\n\nVersion `v1.4.2`contains a patch. Users should upgrade to the patched release as soon as it is available.\n\n### Workarounds\n\nIf developers cannot upgrade their applications immediately:\n\n- ** 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.json` endpoints will need to be granted explicit access or must receive an exported file version until the patched release is deployed.\n\n### Resources\nFixed commit: https://github.com/l3montree-dev/devguard/commit/1be88ec1309a5dc0566e35a23bdc4ea3ecd11417\n\n### Credit\n\nDeevGuard thanks @philipflohr ([awesome-it.de](https://awesome-it.de/)) for finding and responsibly reporting this vulnerability!",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/l3montree-dev/devguard"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.4.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/l3montree-dev/devguard/security/advisories/GHSA-6p54-fw2f-q7gf"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48089"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/l3montree-dev/devguard/commit/1be88ec1309a5dc0566e35a23bdc4ea3ecd11417"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/l3montree-dev/devguard"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-11T20:26:18Z",
    "nvd_published_at" : "2026-06-19T20:16:16Z"
  }
}