CVE-2026-33401: CWE-918: Server-Side Request Forgery (SSRF) in ellite Wallos
CVE-2026-33401 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in ellite Wallos versions prior to 4. 7. 0. It allows an authenticated user to send crafted requests to internal network services, cloud metadata endpoints (AWS, GCP, Azure), or localhost services via unprotected parameters and endpoints. Although a previous patch addressed SSRF on notification test endpoints, three other attack surfaces remained vulnerable: the AI Ollama host parameter, AI recommendations endpoint, and notification cron job. Exploitation requires authentication but no user interaction. The vulnerability has been fixed in version 4. 7. 0. Organizations using affected versions risk unauthorized internal network access and potential data exposure.
AI Analysis
Technical Summary
CVE-2026-33401 is a Server-Side Request Forgery (SSRF) vulnerability affecting ellite Wallos, an open-source, self-hostable personal subscription tracker. Prior to version 4.7.0, although a patch (CVE-2026-30840) addressed SSRF protection on notification test endpoints, three other critical endpoints remained vulnerable: the AI Ollama host parameter, the AI recommendations endpoint, and the notification cron job. An authenticated attacker can exploit these unprotected endpoints by supplying crafted URLs that cause the server to make unauthorized requests to internal network services, localhost-bound services, or cloud metadata endpoints such as AWS IMDSv1, Google Cloud Platform, and Azure Instance Metadata Service. This can lead to unauthorized access to sensitive internal resources, potentially exposing confidential information or enabling further attacks within the internal network. The vulnerability does not require user interaction but does require authentication, which limits exploitation to users with some level of access. The issue was patched in Wallos version 4.7.0, closing these attack surfaces. The CVSS 4.0 base score is 7.1 (high), reflecting network attack vector, low attack complexity, no privileges required beyond authentication, and high impact on confidentiality. No known exploits are currently reported in the wild.
Potential Impact
The SSRF vulnerability allows authenticated users to pivot from the application to internal network resources, which are typically inaccessible externally. This can lead to unauthorized disclosure of sensitive internal data, including cloud metadata endpoints that may contain credentials or tokens granting further access to cloud resources. Exploitation could enable attackers to enumerate internal services, access localhost-only services, or escalate privileges by abusing exposed internal APIs. For organizations, this can result in data breaches, lateral movement within internal networks, and compromise of cloud infrastructure. The impact is especially critical for organizations relying on Wallos for subscription tracking integrated with AI features or cloud services. Since the vulnerability requires authentication, insider threats or compromised accounts pose a significant risk. The absence of user interaction lowers the barrier for exploitation once authenticated access is obtained.
Mitigation Recommendations
The primary mitigation is to upgrade Wallos installations to version 4.7.0 or later, which patches the SSRF vulnerabilities across all affected endpoints. Organizations should audit and restrict access to internal network services and cloud metadata endpoints from application servers, implementing network segmentation and firewall rules to limit outbound requests. Additionally, review and harden authentication mechanisms to prevent unauthorized access to the application. Implement strict input validation and URL allowlisting on any parameters that trigger server-side requests. Monitoring and logging outbound requests from the application can help detect anomalous SSRF attempts. For cloud environments, enforce the use of IMDSv2 or equivalent metadata service protections to reduce risk from SSRF attacks. Regularly review and update dependencies and apply security patches promptly.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, Netherlands, France, Japan, South Korea, India
CVE-2026-33401: CWE-918: Server-Side Request Forgery (SSRF) in ellite Wallos
Description
CVE-2026-33401 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in ellite Wallos versions prior to 4. 7. 0. It allows an authenticated user to send crafted requests to internal network services, cloud metadata endpoints (AWS, GCP, Azure), or localhost services via unprotected parameters and endpoints. Although a previous patch addressed SSRF on notification test endpoints, three other attack surfaces remained vulnerable: the AI Ollama host parameter, AI recommendations endpoint, and notification cron job. Exploitation requires authentication but no user interaction. The vulnerability has been fixed in version 4. 7. 0. Organizations using affected versions risk unauthorized internal network access and potential data exposure.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33401 is a Server-Side Request Forgery (SSRF) vulnerability affecting ellite Wallos, an open-source, self-hostable personal subscription tracker. Prior to version 4.7.0, although a patch (CVE-2026-30840) addressed SSRF protection on notification test endpoints, three other critical endpoints remained vulnerable: the AI Ollama host parameter, the AI recommendations endpoint, and the notification cron job. An authenticated attacker can exploit these unprotected endpoints by supplying crafted URLs that cause the server to make unauthorized requests to internal network services, localhost-bound services, or cloud metadata endpoints such as AWS IMDSv1, Google Cloud Platform, and Azure Instance Metadata Service. This can lead to unauthorized access to sensitive internal resources, potentially exposing confidential information or enabling further attacks within the internal network. The vulnerability does not require user interaction but does require authentication, which limits exploitation to users with some level of access. The issue was patched in Wallos version 4.7.0, closing these attack surfaces. The CVSS 4.0 base score is 7.1 (high), reflecting network attack vector, low attack complexity, no privileges required beyond authentication, and high impact on confidentiality. No known exploits are currently reported in the wild.
Potential Impact
The SSRF vulnerability allows authenticated users to pivot from the application to internal network resources, which are typically inaccessible externally. This can lead to unauthorized disclosure of sensitive internal data, including cloud metadata endpoints that may contain credentials or tokens granting further access to cloud resources. Exploitation could enable attackers to enumerate internal services, access localhost-only services, or escalate privileges by abusing exposed internal APIs. For organizations, this can result in data breaches, lateral movement within internal networks, and compromise of cloud infrastructure. The impact is especially critical for organizations relying on Wallos for subscription tracking integrated with AI features or cloud services. Since the vulnerability requires authentication, insider threats or compromised accounts pose a significant risk. The absence of user interaction lowers the barrier for exploitation once authenticated access is obtained.
Mitigation Recommendations
The primary mitigation is to upgrade Wallos installations to version 4.7.0 or later, which patches the SSRF vulnerabilities across all affected endpoints. Organizations should audit and restrict access to internal network services and cloud metadata endpoints from application servers, implementing network segmentation and firewall rules to limit outbound requests. Additionally, review and harden authentication mechanisms to prevent unauthorized access to the application. Implement strict input validation and URL allowlisting on any parameters that trigger server-side requests. Monitoring and logging outbound requests from the application can help detect anomalous SSRF attempts. For cloud environments, enforce the use of IMDSv2 or equivalent metadata service protections to reduce risk from SSRF attacks. Regularly review and update dependencies and apply security patches promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-19T17:02:34.170Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c2d885f4197a8e3b5f9738
Added to database: 3/24/2026, 6:31:33 PM
Last enriched: 3/24/2026, 6:46:23 PM
Last updated: 3/24/2026, 7:35:15 PM
Views: 3
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.