{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25123 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25123 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25123 is a medium-severity server-side request forgery vulnerability in homarr-labs homarr, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25123 and fix it if it is affected.\n\nWhat it is: CVE-2026-25123 is a medium-severity server-side request forgery vulnerability in homarr-labs homarr, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25123 in the wild and no public exploit code.\n\nAffected product: homarr-labs homarr. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25123/ (Markdown: https://insights.sbomify.com/CVE-2026-25123/index.md)","id":"CVE-2026-25123","markdown":"https://insights.sbomify.com/CVE-2026-25123/index.md","name":"CVE-2026-25123","record":{"aliases":["GHSA-c6rh-8wj4-gv74"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Homarr dashboard","requires_auth":"none","summary":"Unauthenticated attackers can exploit an SSRF vulnerability in Homarr to perform server-side requests and port scans.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"homarr","vendor":"homarr"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Homarr affected by Unauthenticated SSRF / Port-Scan Primitive via widget.app.ping","id":"CVE-2026-25123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenEMR has Broken Access Control in Report/Clients/Message List CSV Export","id":"CVE-2026-25124"},"packages":[],"prev":{"headline":"apko is vulnerable to unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams","id":"CVE-2026-25122"},"products":["homarr"],"published":"2026-02-06","related":[{"cvss_score":8.8,"headline":"DOM-Based XSS in Homarr /auth/login Redirect","id":"CVE-2026-33510","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.1,"headline":"Homarr is Vulnerable to Stored Cross-Site Scripting (XSS) and Possible Privilege Escalation via Malicious SVG Upload","id":"CVE-2025-64759","kev_date_added":null,"published":"2025-11-19"},{"cvss_score":7.5,"headline":"Homarr: missing input sanitization and possible privilege escalation through ldap search query injection","id":"CVE-2025-67493","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":5.3,"headline":"Homarr: Unauthenticated Information Disclosure (Integration Metadata Leak)","id":"CVE-2026-27796","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":5.3,"headline":"Homarr: Unauthenticated SSRF in rssFeed.ts","id":"CVE-2026-27797","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":4.2,"headline":"Homarr has a Race Condition in Invite Token Registration (TOCTOU)","id":"CVE-2026-32602","kev_date_added":null,"published":"2026-04-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-09","vendors":["homarr-labs"]},"summary":"Unauthenticated attackers can exploit an SSRF vulnerability in Homarr to perform server-side requests and port scans.","url":"https://insights.sbomify.com/CVE-2026-25123/"}