CVE-2026-27797: CWE-918: Server-Side Request Forgery (SSRF) in homarr-labs homarr
Homarr is an open-source dashboard. Prior to version 1.54.0, an unauthenticated Server-Side Request Forgery (SSRF) vulnerability allows a remote attacker to force the Homarr server to perform arbitrary outbound HTTP requests. This can be used as an internal network access primitive (e.g., reaching loopback/private ranges) from the Homarr host/container network context. This issue has been patched in version 1.54.0.
AI Analysis
Technical Summary
CVE-2026-27797 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Homarr open-source dashboard software prior to version 1.54.0. SSRF vulnerabilities occur when an attacker can manipulate a server to send HTTP requests to arbitrary destinations, often leading to unauthorized internal network access. In this case, the vulnerability allows unauthenticated remote attackers to coerce the Homarr server into making arbitrary outbound HTTP requests. This can be leveraged to reach internal network resources, such as loopback addresses (e.g., 127.0.0.1) or private IP ranges (e.g., 10.x.x.x, 192.168.x.x), which are typically inaccessible from outside the network. The attack surface includes the Homarr host or container network context, meaning that the attacker can pivot from the exposed Homarr service to internal services that may not be directly exposed to the internet. The vulnerability does not require any authentication or user interaction, increasing its risk profile. However, the CVSS score of 5.3 reflects that the impact on confidentiality is limited (partial information disclosure), with no direct impact on integrity or availability. The vulnerability was publicly disclosed on March 7, 2026, and has been patched in Homarr version 1.54.0. No known exploits have been reported in the wild to date. The vulnerability is classified under CWE-918, which covers SSRF issues. Given the nature of SSRF, attackers could potentially use this flaw to perform reconnaissance, access internal APIs, or exploit other internal vulnerabilities, depending on the network environment and services running internally.
Potential Impact
The primary impact of CVE-2026-27797 is unauthorized internal network access via SSRF, which can lead to information disclosure of internal services or metadata endpoints. Organizations running vulnerable versions of Homarr expose their internal network infrastructure to remote attackers without requiring authentication. This can facilitate further attacks such as internal service enumeration, exploitation of internal vulnerabilities, or lateral movement within the network. Although the vulnerability does not directly compromise integrity or availability, the ability to access internal resources can be a stepping stone for more severe attacks. The risk is higher in environments where Homarr is deployed in containerized or cloud environments with sensitive internal services accessible only via internal IPs. The medium CVSS score reflects the moderate severity, but the actual impact depends on the internal network architecture and what services are accessible internally. Organizations with sensitive internal APIs or metadata services exposed internally are at greater risk. Since no known exploits are reported yet, the threat is currently theoretical but should be treated proactively due to the ease of exploitation and lack of authentication requirements.
Mitigation Recommendations
To mitigate CVE-2026-27797, organizations should immediately upgrade Homarr to version 1.54.0 or later, where the SSRF vulnerability has been patched. If upgrading is not immediately possible, implement network-level restrictions to limit outbound HTTP requests from the Homarr server or container, using firewall rules or egress filtering to prevent unauthorized internal network access. Additionally, apply strict input validation and sanitization on any user-controllable parameters that influence outbound requests, if applicable. Employ network segmentation to isolate Homarr servers from sensitive internal services and metadata endpoints. Monitor network traffic for unusual outbound requests originating from Homarr instances. Consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities to block suspicious request patterns. Finally, conduct regular security assessments and penetration tests focusing on SSRF and internal network exposure to identify and remediate similar issues proactively.
Affected Countries
United States, Germany, France, United Kingdom, Canada, Australia, Netherlands, Japan, South Korea, India
CVE-2026-27797: CWE-918: Server-Side Request Forgery (SSRF) in homarr-labs homarr
Description
Homarr is an open-source dashboard. Prior to version 1.54.0, an unauthenticated Server-Side Request Forgery (SSRF) vulnerability allows a remote attacker to force the Homarr server to perform arbitrary outbound HTTP requests. This can be used as an internal network access primitive (e.g., reaching loopback/private ranges) from the Homarr host/container network context. This issue has been patched in version 1.54.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-27797 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Homarr open-source dashboard software prior to version 1.54.0. SSRF vulnerabilities occur when an attacker can manipulate a server to send HTTP requests to arbitrary destinations, often leading to unauthorized internal network access. In this case, the vulnerability allows unauthenticated remote attackers to coerce the Homarr server into making arbitrary outbound HTTP requests. This can be leveraged to reach internal network resources, such as loopback addresses (e.g., 127.0.0.1) or private IP ranges (e.g., 10.x.x.x, 192.168.x.x), which are typically inaccessible from outside the network. The attack surface includes the Homarr host or container network context, meaning that the attacker can pivot from the exposed Homarr service to internal services that may not be directly exposed to the internet. The vulnerability does not require any authentication or user interaction, increasing its risk profile. However, the CVSS score of 5.3 reflects that the impact on confidentiality is limited (partial information disclosure), with no direct impact on integrity or availability. The vulnerability was publicly disclosed on March 7, 2026, and has been patched in Homarr version 1.54.0. No known exploits have been reported in the wild to date. The vulnerability is classified under CWE-918, which covers SSRF issues. Given the nature of SSRF, attackers could potentially use this flaw to perform reconnaissance, access internal APIs, or exploit other internal vulnerabilities, depending on the network environment and services running internally.
Potential Impact
The primary impact of CVE-2026-27797 is unauthorized internal network access via SSRF, which can lead to information disclosure of internal services or metadata endpoints. Organizations running vulnerable versions of Homarr expose their internal network infrastructure to remote attackers without requiring authentication. This can facilitate further attacks such as internal service enumeration, exploitation of internal vulnerabilities, or lateral movement within the network. Although the vulnerability does not directly compromise integrity or availability, the ability to access internal resources can be a stepping stone for more severe attacks. The risk is higher in environments where Homarr is deployed in containerized or cloud environments with sensitive internal services accessible only via internal IPs. The medium CVSS score reflects the moderate severity, but the actual impact depends on the internal network architecture and what services are accessible internally. Organizations with sensitive internal APIs or metadata services exposed internally are at greater risk. Since no known exploits are reported yet, the threat is currently theoretical but should be treated proactively due to the ease of exploitation and lack of authentication requirements.
Mitigation Recommendations
To mitigate CVE-2026-27797, organizations should immediately upgrade Homarr to version 1.54.0 or later, where the SSRF vulnerability has been patched. If upgrading is not immediately possible, implement network-level restrictions to limit outbound HTTP requests from the Homarr server or container, using firewall rules or egress filtering to prevent unauthorized internal network access. Additionally, apply strict input validation and sanitization on any user-controllable parameters that influence outbound requests, if applicable. Employ network segmentation to isolate Homarr servers from sensitive internal services and metadata endpoints. Monitor network traffic for unusual outbound requests originating from Homarr instances. Consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities to block suspicious request patterns. Finally, conduct regular security assessments and penetration tests focusing on SSRF and internal network exposure to identify and remediate similar issues proactively.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-24T02:31:33.266Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69abbf1fc48b3f10ff5c73ae
Added to database: 3/7/2026, 6:01:03 AM
Last enriched: 3/14/2026, 7:45:00 PM
Last updated: 4/21/2026, 11:42:24 AM
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.