CVE-2026-25123
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHomarr 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHomarr dashboard versions prior to 1.52.0 contain an unauthenticated SSRF vulnerability in the public tRPC endpoint widget.app.ping. This endpoint accepts arbitrary URLs and performs server-side HTTP requests, allowing attackers to trigger outbound requests from the Homarr server for port scanning and internal resource access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.52.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Homarr versionLocate the Homarr instance and determine its version number. Check the web UI footer, container image tag, docker-compose file, or package.json in the installation directory.Affected if Version is below 1.52.0
-
Confirm network exposureDetermine if the Homarr dashboard is accessible from non-localhost network locations. This can be verified by checking the bind address configuration or by attempting to access the UI from another machine.Affected if Homarr is listening on a non-localhost interface and version is below 1.52.0
-
Test widget.app.ping endpoint for SSRFSend a request to the public tRPC endpoint widget.app.ping with an arbitrary URL such as http://127.0.0.1:PORT or an internal hostname, then verify if the server performs the outbound HTTP request.Affected if The server successfully makes HTTP requests to URLs supplied in the widget.app.ping parameter, indicating the SSRF vulnerability is present
If Homarr version is below 1.52.0 and the dashboard is network-accessible, the environment is affected by this unauthenticated SSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.52.0
Upgrade Homarr to version 1.52.0 or later. If immediate upgrade is not possible, consider network-level controls to restrict outbound HTTP/S traffic from the Homarr server.
1.52.0
- Backup your current Homarr installation and any important data
- Stop the Homarr service
- Upgrade Homarr to version 1.52.0 or later using your deployment method (e.g., Docker pull, package manager, or binary update)
- Restart the Homarr service
- Verify the upgrade was successful and the application is running normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25123 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25123 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data