{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27796 exists.","fix":"No fix has been published for CVE-2026-27796 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27796 is a medium-severity vulnerability in homarr-labs homarr, published on 7 Mar 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-27796 and fix it if it is affected.\n\nWhat it is: CVE-2026-27796 is a medium-severity vulnerability in homarr-labs homarr, published on 7 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27796 exists.\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-27796/ (Markdown: https://insights.sbomify.com/CVE-2026-27796/index.md)","id":"CVE-2026-27796","markdown":"https://insights.sbomify.com/CVE-2026-27796/index.md","name":"CVE-2026-27796","record":{"aliases":["GHSA-m4vc-4prp-cvp7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Homarr dashboard","requires_auth":"none","summary":"Unauthenticated attackers can access sensitive integration metadata, including internal service URLs, via a public tRPC endpoint in Homarr.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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-862","name":"Missing Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Homarr is an open-source dashboard. Prior to version 1.54.0, the integration.all tRPC endpoint in Homarr is exposed as a publicProcedure, allowing unauthenticated users to retrieve a complete list of configured integrations. This metadata includes sensitive information such as internal service URLs, integration names, and service types. This issue has been patched in version 1.54.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-27796.yaml","stars":null,"title":"Homarr \u003c 1.54.0 - Information Disclosure"}],"tier":"weaponised"},"has_fix":false,"headline":"Homarr: Unauthenticated Information Disclosure (Integration Metadata Leak)","id":"CVE-2026-27796","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Homarr: Unauthenticated SSRF in rssFeed.ts","id":"CVE-2026-27797"},"packages":[],"prev":{"headline":"LangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader","id":"CVE-2026-27795"},"products":["homarr"],"published":"2026-03-07","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 SSRF in rssFeed.ts","id":"CVE-2026-27797","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":5.3,"headline":"Homarr affected by Unauthenticated SSRF / Port-Scan Primitive via widget.app.ping","id":"CVE-2026-25123","kev_date_added":null,"published":"2026-02-06"},{"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["homarr-labs"]},"summary":"Unauthenticated attackers can access sensitive integration metadata, including internal service URLs, via a public tRPC endpoint in Homarr.","url":"https://insights.sbomify.com/CVE-2026-27796/"}