Cross-organization data tampering via public-read exemption
Published Jun 19, 2026 · Updated Jun 19, 2026
Incorrect authorization in l3montree GmbH DevGuard before 1.4.2 allows remote authenticated users to alter public-asset triage data. The asset access-control middleware treated public-read context as sufficient while write routes lacked public-request rejection or asset-scoped RBAC checks. A valid instance account and a public victim asset are required; successful requests can falsify VEX/SBOM-derived decisions or delete legitimate triage state.
Summary
What happened
Incorrect authorization in l3montree GmbH DevGuard before 1.4.2 allows remote authenticated users to alter public-asset triage data. The asset access-control middleware treated public-read context as sufficient while write routes lacked public-request rejection or asset-scoped RBAC checks. A valid instance account and a public victim asset are required; successful requests can falsify VEX/SBOM-derived decisions or delete legitimate triage state.
The record
- CVE
- CVE-2026-48089
- Published
- Jun 19, 2026
- Updated
- Jun 19, 2026
- Vendor
- l3montree GmbH
- Product
- DevGuard
- Classifications
- CWE-863, CWE-285, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2026CVE publishedPublication date reported by the CVE source.
- Jun 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo