Homarr is an open-source dashboard application that prior to version 1.54.0 contained a vulnerability identified as CVE-2026-27796. The vulnerability arises because the integration.all tRPC endpoint is exposed as a publicProcedure, meaning it can be accessed without any authentication or authorization checks. This endpoint returns a comprehensive list of all configured integrations within the Homarr instance, including sensitive metadata such as internal service URLs, integration names, and service types. Such information exposure falls under CWE-200, indicating exposure of sensitive information to unauthorized actors, and CWE-862, indicating missing authorization. The vulnerability is remotely exploitable over the network without any user interaction or privileges, making it relatively easy to exploit. However, the impact is limited to confidentiality as no integrity or availability impacts are reported. The CVSS v3.1 score is 5.3 (medium severity), reflecting the ease of access but limited impact scope. The vulnerability was publicly disclosed and patched in version 1.54.0 of Homarr. No known exploits are currently reported in the wild. This vulnerability could be leveraged by attackers to gather intelligence about internal services and integrations, potentially facilitating further targeted attacks or lateral movement within a network.

The primary impact of this vulnerability is the unauthorized disclosure of sensitive configuration data, which can compromise the confidentiality of internal network architecture and services. Attackers gaining access to internal service URLs and integration details can use this information for reconnaissance, enabling more effective phishing, social engineering, or direct attacks against exposed services. While the vulnerability does not directly affect system integrity or availability, the leaked information could be a stepping stone for more severe attacks. Organizations relying on Homarr dashboards for managing critical integrations may inadvertently expose sensitive operational details, increasing their attack surface. This risk is particularly significant for enterprises with complex internal services or those operating in regulated industries where information leakage can lead to compliance violations or reputational damage.

To mitigate this vulnerability, organizations should upgrade Homarr installations to version 1.54.0 or later, where the issue has been patched. Until upgrading is possible, administrators should restrict network access to the integration.all tRPC endpoint, ensuring it is not accessible from untrusted networks or the public internet. Implementing network segmentation and firewall rules to limit access to the Homarr dashboard can reduce exposure. Additionally, reviewing and enforcing strict authentication and authorization policies for all API endpoints is critical to prevent unauthorized data access. Monitoring access logs for unusual or unauthorized requests to the integration.all endpoint can help detect exploitation attempts. Finally, organizations should conduct regular security audits of their dashboards and integrations to identify and remediate similar information disclosure risks proactively.