Skip to main content
Mallory
MediumVulnerability

CVE-2026-64964: Predictable Account Activation Token in ATutor

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.36%31st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Atutor
IdentifiersCVE-2026-64964CWE-340 · Generation of Predictable Numbers…

ATutor contains a predictable token vulnerability in its account confirmation workflow. The application generates email confirmation or account activation tokens using insufficiently random, registration-related values, making the resulting tokens guessable by an attacker who knows or can predict those inputs. As a result, valid activation tokens for unconfirmed accounts can be derived without access to the intended recipient's email inbox. The issue was confirmed in ATutor 2.2.4, and other versions may also be affected.

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 allows an attacker to activate an unconfirmed account without controlling the associated email account. This undermines the integrity of the registration and email-verification process, enabling unauthorized account activation and potentially facilitating fraudulent account creation or use of accounts that should have remained inaccessible until email ownership was verified.

Mitigation

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

If immediate migration is not possible, reduce exposure by disabling or tightly restricting self-service registration and account confirmation workflows where feasible. Apply compensating controls such as limiting access to the application, placing the service behind additional access restrictions, and closely monitoring registration and activation activity for abuse. Because no vendor fix is available, mitigation should be treated as temporary risk reduction rather than a complete solution.

Remediation

Patch, then assume compromise.

No patch is available. ATutor is no longer actively supported and the vulnerability has not been fixed. The recommended remediation is to migrate from ATutor 2.2.4 and any other potentially affected unsupported versions to a supported alternative or maintained fork, and decommission or isolate vulnerable deployments.

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-64964 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-64964 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-64964?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-64964.
Is there a patch for CVE-2026-64964?
No patch is available. ATutor is no longer actively supported and the vulnerability has not been fixed.
What products are affected by CVE-2026-64964?
Atutor.
How severe is CVE-2026-64964?
CVE-2026-64964 has a CVSS v4 score of 6.3 (Medium) and an EPSS score of 0.36% (31st 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.