External risk intelligence

Homarr LDAP Authentication Privilege Escalation

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2025-67493

Homarr is a dashboard application designed for organizing services and apps, which is frequently deployed as a web-accessible interface. Because it is a web-based dashboard often intended for user access and service management, it is commonly exposed to network or internet environments, placing the vulnerable authentication and input processing logic within a likely-to-be-reached surface.

Privilege Escalation

Homarr

before 1.45.3

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Homarr, an open-source dashboard used for organizing services. If Homarr is configured to use LDAP for authentication and an attacker gains access to a user account, they could potentially escalate their privileges and access other users' groups. The main concern is confirming if your environment uses Homarr with LDAP authentication and if any user accounts have been compromised.

  • User input errors allow unauthorized access.
  • It impacts user data and system control.
  • Confirm Homarr LDAP use and exposure.

Attack Path

How an attacker could exploit the issue

An attacker with a user account could leverage a flaw in how Homarr handles LDAP search queries. By submitting specially crafted input, an attacker might gain elevated privileges and access other users' data. This could happen in any Homarr instance that uses LDAP for authentication and is exposed to a malicious actor who has already compromised a user account.

  • Requires authenticated user account.
  • Triggered by crafted LDAP search input.
  • Leads to privilege escalation and data access.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, Homarr instances using LDAP authentication could be vulnerable to privilege escalation if a malicious actor gains access to a user account. This occurs due to improperly sanitized inputs in the LDAP search query, potentially affecting access to other users' group information.

  • User group data could be at risk.
  • Malicious actor leverages a user account.
  • Unauthorized access to other user groups.

Operational Fix

Recommended remediation, mitigation, and detection steps

In real-world scenarios, application owners and platform teams are typically responsible for Homarr, especially when it's used for managing other services and incorporates LDAP authentication. The first practical step involves identifying all Homarr instances, confirming their network exposure and business criticality, and then locating the accountable owner to plan a risk-based remediation strategy.

  • Application owners should manage this issue.
  • Verify LDAP authentication and reachability first.
  • Coordinate vendor updates and plan remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Homarr?

Homarr is an open-source, self-hosted dashboard application. People use it as a central hub to organize, monitor, and access their various services and web applications from a single browser-based interface.

What does CVE-2025-67493 mean for security?

This CVE represents a vulnerability where missing input sanitization allows an attacker to manipulate LDAP search queries. Categorized under CWE-20 (Improper Input Validation) and CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query), it enables privilege escalation and unauthorized access to other users' group information.

How is this vulnerability triggered?

An attacker triggers this by submitting specifically crafted input into the system while authenticated as a user. It does not occur if LDAP authentication is disabled or if the instance is not actively processing these malicious search queries.

Is my Homarr instance at risk?

Risk is high for instances using LDAP authentication. Halo Surface Signal identifies Homarr as a web-based dashboard frequently deployed in network-accessible environments, meaning it is often positioned in a surface area where remote actors could reach the vulnerable authentication logic.

What should I do to address this?

First, verify if your instance uses LDAP for authentication. If it does, determine your current version; update to version 1.45.3 or later to apply the necessary patch that secures how the application handles search queries.

References