CVE-2026-26273: idno known · Information Exposure
Affects idno knownSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.6.3 as a priority.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.6.3
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade idno known to 1.6.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| idnoknown | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-26273, organizations should immediately upgrade Known installations to version 1.6.3 or later, where the vulnerability is patched. Beyond upgrading, administrators should audit password reset workflows to ensure sensitive tokens are never exposed client-side or in any user-accessible content. Implement server-side validation and token handling that requires authentication or additional verification steps before allowing password resets. Employ rate limiting and monitoring on password reset endpoints to detect and block mass enumeration attempts. Consider implementing multi-factor authentication (MFA) to reduce the impact of account takeovers. Regularly review and update security controls around authentication and password recovery mechanisms. Finally, educate users about suspicious activity and encourage strong, unique passwords to further reduce risk.
Description
Known is a social publishing platform. Prior to 1.6.3, a Critical Broken Authentication vulnerability exists in Known 1.6.2 and earlier. The application leaks the password reset token within a hidden HTML input field on the password reset page. This allows any unauthenticated attacker to retrieve the reset token for any user by simply querying the user's email, leading to full Account Takeover (ATO) without requiring access to the victim's email inbox. This vulnerability is fixed in 1.6.3.