CVE-2026-25123VulnerabilityPublished 6 Feb 2026Updated 9 Feb 2026

CVE-2026-25123: homarr · Server-Side Request Forgery (SSRF)

Affects homarrSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.52.0 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.52.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade homarr and homarr-labs/homarr to 1.52.0.

Affected software

Product	Affected	Fixed in
homarr-labshomarr	Affected <1.52.0	Fixed in 1.52.0
GitHubhomarr-labs/homarr`pkg:github/homarr-labs/homarr`Other threats	Affected <1.52.0	Fixed in 1.52.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Homarr to version 1.52.0 or later immediately to apply the official fix for CVE-2026-25123. 2. If upgrading is not immediately possible, implement network-level controls to restrict outbound HTTP requests from the Homarr server, limiting its ability to reach internal or sensitive network resources. 3. Employ strict input validation and filtering on any exposed endpoints that accept URLs or network addresses to prevent SSRF attempts. 4. Monitor server logs for unusual outbound request patterns originating from the Homarr server, which may indicate exploitation attempts. 5. Use network segmentation to isolate the Homarr server from critical internal systems, reducing the impact of any SSRF-based reconnaissance. 6. Implement Web Application Firewalls (WAFs) with rules to detect and block SSRF attack patterns targeting the widget.app.ping endpoint. 7. Conduct regular security assessments and penetration tests focusing on SSRF and related vulnerabilities in internal dashboards or management tools. 8. Educate development and operations teams about SSRF risks and secure coding practices to prevent similar vulnerabilities in future.

Description

Homarr is an open-source dashboard. Prior to 1.52.0, a public (unauthenticated) tRPC endpoint widget.app.ping accepts an arbitrary url and performs a server-side request to that URL. This allows an unauthenticated attacker to trigger outbound HTTP requests from the Homarr server, enabling SSRF behavior and a reliable port-scanning primitive (open vs closed ports can be inferred from statusCode vs fetch failed and timing). This vulnerability is fixed in 1.52.0.

Impact

For European organizations, this SSRF vulnerability poses a moderate risk primarily related to confidentiality breaches. Attackers can leverage the vulnerability to perform internal network reconnaissance, identifying open ports and services that are not exposed externally. This can lead to the discovery of sensitive internal infrastructure, increasing the risk of subsequent targeted attacks such as lateral movement, exploitation of internal services, or data exfiltration. While the vulnerability does not directly impact data integrity or system availability, the information gained can be a critical enabler for more damaging attacks. Organizations using Homarr dashboards in critical sectors such as finance, government, healthcare, or industrial control systems could be particularly at risk if internal network details are exposed. The unauthenticated nature of the exploit increases the threat as attackers do not need valid credentials or user interaction. However, the medium CVSS score reflects that the vulnerability alone does not allow direct compromise beyond information gathering. The absence of known exploits in the wild reduces immediate risk but does not eliminate the need for prompt remediation.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/homarr-labs/homarr/security/advisories/GHSA-c6rh-8wj4-gv74 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Feb 2026, 12:09 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats