CVE-2026-33401
UNKNOWNCVE-2026-33401 is an incomplete SSRF patch in Wallos that left three endpoints unprotected, including the AI Ollama host configuration parameter. Any authenticated user can point the Ollama host to AWS IMDSv1 (169.254.169.254) or equivalent cloud metadata endpoints to harvest IAM credentials and pivot to your cloud environment. If you run Wallos in AWS, GCP, or Azure without IMDSv2 enforcement, treat this as critical — patch to 4.7.0 immediately and enforce IMDSv2 on all instances.
Severity & Risk
Recommended Action
- 1. Patch immediately to Wallos 4.7.0. 2. On AWS: enforce IMDSv2 (hop limit=1) on all EC2 instances running Wallos — this blocks SSRF to the metadata service even if unpatched. 3. On GCP/Azure: verify metadata server access controls and consider instance-level firewall rules blocking 169.254.169.254. 4. Audit logs for suspicious outbound HTTP requests from your Wallos instance, particularly to RFC1918 ranges, 169.254.169.254, or 100.100.100.200. 5. Network-level: restrict Wallos host egress to only required destinations (Ollama endpoint, notification providers). 6. Review all user-configurable URL/host parameters in any AI-integrated self-hosted app for SSRF controls.
Classification
Compliance Impact
This CVE is relevant to:
Technical Details
NVD Description
Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.7.0, the patch introduced in commit e8a513591 (CVE-2026-30840) added SSRF protection to notification test endpoints but left three additional attack surfaces unprotected: the AI Ollama host parameter, the AI recommendations endpoint, and the notification cron job. An authenticated user can reach internal network services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure IMDS), or localhost-bound services by supplying a crafted URL to any of these endpoints. This issue has been patched in version 4.7.0.
Exploitation Scenario
Authenticated attacker logs into a cloud-hosted Wallos instance. In the AI settings, they set the Ollama host parameter to http://169.254.169.254/latest/meta-data/iam/security-credentials/. The Wallos application makes an outbound request to this URL and returns the response — including temporary AWS IAM credentials with the instance role permissions. Attacker extracts AccessKeyId, SecretAccessKey, and Token, then uses them via AWS CLI to enumerate S3 buckets, read secrets from Secrets Manager, or pivot to other AWS services. The notification cron job endpoint provides an alternative trigger that fires automatically, removing the need for repeated manual interaction.
Weaknesses (CWE)
References
- github.com/ellite/Wallos/commit/e87387f0ebb540cd33e6dfda7181db9db650ecef
- github.com/ellite/Wallos/commit/e87387f0ebb540cd33e6dfda7181db9db650ecef
- github.com/ellite/Wallos/commit/e8a513591
- github.com/ellite/Wallos/commit/e8a513591
- github.com/ellite/Wallos/security/advisories/GHSA-r82v-p8cg-rgx3
- github.com/ellite/Wallos/security/advisories/GHSA-r82v-p8cg-rgx3