Skip to main content
Mallory
MediumVulnerability

CVE-2026-64961: Authentication Bypass in ATutor Auto-Login

Published Aug 20, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.3Medium · v4
EPSS0.48%42nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Atutor
IdentifiersCVE-2026-64961CWE-639 · Authorization Bypass Through…

CVE-2026-64961 is an authentication bypass vulnerability in ATutor, confirmed in version 2.2.4. The flaw affects the application's auto-login functionality. Although the code includes a token validation check, the values required for that validation remain uninitialized in certain execution paths. As a result, an unauthenticated attacker who can determine a target user's identifier and registration timestamp can generate a token that passes validation and log in as that user without knowing the account password. The issue can be used to impersonate any existing account, including administrative users.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in full account takeover of any targeted ATutor user whose identifier and registration timestamp can be determined. If an administrator account is impersonated, the attacker can obtain complete administrative control over the ATutor instance, enabling unauthorized access to application data and administrative functions, and potentially facilitating broader compromise depending on the privileges and integrations available to that account.

Mitigation

If you can’t patch tonight, do this now.

Because no vendor patch exists, exposure should be reduced operationally. Remove public internet exposure where possible, restrict access to trusted networks or users only, and closely monitor authentication activity for anomalous logins or unexpected account access. If continued operation is unavoidable, isolate the application from sensitive internal systems and disable the vulnerable auto-login functionality through local modification if feasible.

Remediation

Patch, then assume compromise.

No official fix is available. ATutor is no longer actively supported and the vulnerability remains unpatched. The recommended remediation is to migrate to a supported alternative or decommission affected ATutor installations. If the application must remain in service temporarily, organizations should implement a local code fix to remove or securely redesign the vulnerable auto-login mechanism and ensure token validation uses properly initialized, cryptographically sound values.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AtutorAtutorapplication
FAQ

Frequently asked questions

Is CVE-2026-64961 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-64961 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-64961?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-64961.
Is there a patch for CVE-2026-64961?
No official fix is available. ATutor is no longer actively supported and the vulnerability remains unpatched.
What products are affected by CVE-2026-64961?
Atutor.
How severe is CVE-2026-64961?
CVE-2026-64961 has a CVSS v4 score of 6.3 (Medium) and an EPSS score of 0.48% (42nd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.