Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NSummary
CVE-2026-27479 is a high-severity SSRF (CWE-918) vulnerability in Wallosapp Wallos. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Wallos, an open-source self-hostable personal subscription tracker, in versions 4.6.0 and below, contains CVE-2026-27479, a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918. The flaw resides in the subscription and payment logo/icon upload functionality, specifically the getLogoFromUrl() function. This function validates the provided URL by resolving its hostname and checking the resulting IP address against private or reserved ranges using FILTER_FLAG_NO_PRIV_RANGE | FILTER_FLAG_NO_RES_RANGE. However, the subsequent cURL request is configured with CURLOPT_FOLLOWLOCATION set to true and CURLOPT_MAXREDIRS to 3, permitting HTTP redirects to destinations without re-validating their IP addresses.
The vulnerability can be exploited by an authenticated attacker with low privileges (PR:L) over the network (AV:N), requiring low attack complexity (AC:L) and no user interaction (UI:N). By supplying a malicious URL that initially resolves to a public IP but redirects to internal resources, the attacker bypasses validation, enabling access to internal services such as cloud instance metadata endpoints. This results in high confidentiality impact (C:H) with a changed scope (S:C) and no integrity or availability effects (I:N/A:N), yielding a CVSS v3.1 base score of 7.7.
Mitigation is addressed in Wallos version 4.6.1, which fixes the SSRF bypass. Security practitioners are advised to upgrade immediately. Details are provided in the GitHub security advisory (GHSA-fgmf-7g5v-jmjg), the v4.6.1 release notes, and the patching commit (76a53df9cb4658123b8f0b7cf1826f1ba7d1c960).
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-7718
Vulnerability Data
Wallos is an open-source, self-hostable personal subscription tracker. Versions 4.6.0 and below contain a Server-Side Request Forgery (SSRF) vulnerability in the subscription and payment logo/icon upload functionality. The application validates the IP address of the provided URL before making the…
more
request, but allows HTTP redirects (CURLOPT_FOLLOWLOCATION = true), enabling an attacker to bypass the IP validation and access internal resources, including cloud instance metadata endpoints. The getLogoFromUrl() function validates the URL by resolving the hostname and checking if the resulting IP is in a private or reserved range using FILTER_FLAG_NO_PRIV_RANGE | FILTER_FLAG_NO_RES_RANGE. However, the subsequent cURL request is configured with CURLOPT_FOLLOWLOCATION = true and CURLOPT_MAXREDIRS = 3, which means the request will follow HTTP redirects without re-validating the destination IP. This issue has been fixed in version 4.6.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.
Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.
Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Network segmentation and egress controls can limit the damage from successful SSRF requests.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.