Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-61641 – OIDC Authentication Bypass / Account Takeover – Wallos 4.0.0–4.9.5

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-61641 is an improper authentication vulnerability (CWE-287) in Wallos, an open-source, self-hostable subscription tracker. Wallos’s OIDC login flow links an incoming OIDC identity to an existing local account by matching the email claim alone, without checking whether the identity provider marked that email as verified. This allows an attacker with no Wallos account to authenticate as another user, including the administrator, resulting in complete account takeover. The issue carries a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: in the OIDC callback handler, when no match is found by subject identifier, the code falls back to matching users by email and automatically links the OIDC identity to that local account, without checking the email_verified field returned by the identity provider.
  • Trigger conditions: OIDC login must be enabled on the Wallos instance, and the configured identity provider must allow a user to present an arbitrary or unverified email address (e.g., multi-tenant IdPs or IdPs with open self-registration).
  • Attack vector: network — an attacker authenticates to the configured IdP with an unverified email matching a victim’s Wallos account email, then completes the OIDC login flow against Wallos.
  • Impact: full account takeover, including of the admin account, granting access to user management, OIDC configuration, and all user subscription data, without needing a password or an existing account.

Affected software

  • Wallos versions 4.0.0 through 4.9.5 (OIDC login feature, introduced in 4.0.0)
  • Fixed in version 4.9.6

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Wallos to version 4.9.6 or later, which enforces verification of the email claim before linking OIDC identities to local accounts.
  • If immediate patching is not possible: Disable OIDC login until upgraded, or restrict OIDC to identity providers that guarantee email_verified is true and cannot be spoofed by self-registering users.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge