Unauthenticated integration metadata disclosure via publicProcedure
Published Mar 7, 2026 · Updated Mar 7, 2026
Missing authorization in Homarr before 1.54.0 allows remote attackers to read configured integration metadata through a tRPC request. The integration.all procedure in packages/api/src/router/integration/integration-router.ts uses publicProcedure and returns integrationSchema records without a session check. Any network client that can reach the dashboard can obtain integration names, service types, and internal service URLs, exposing network topology without changing data.
Summary
What happened
Missing authorization in Homarr before 1.54.0 allows remote attackers to read configured integration metadata through a tRPC request. The integration.all procedure in packages/api/src/router/integration/integration-router.ts uses publicProcedure and returns integrationSchema records without a session check. Any network client that can reach the dashboard can obtain integration names, service types, and internal service URLs, exposing network topology without changing data.
The record
- CVE
- CVE-2026-27796
- Published
- Mar 7, 2026
- Updated
- Mar 7, 2026
- Vendor
- Homarr
- Product
- Homarr
- Classifications
- CWE-862, CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 7, 2026CVE publishedPublication date reported by the CVE source.
- Mar 7, 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.54.0
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
- integration.all curl proof of conceptproof of concept · demonstrated
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