Skip to main content
VulnerabilityPublished

CVE-2026-28275: Morelitea initiative · Insufficient Session Expiration

Affects Morelitea initiativeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 0.32.4 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.32.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade initiative and morelitea/initiative to 0.32.4.

Affected software

ProductAffectedFixed in
MoreliteainitiativeAffected
  • <0.32.4
Fixed in
  • 0.32.4
GitHubmorelitea/initiativepkg:github/morelitea/initiativeOther threatsAffected
  • <0.32.4
Fixed in
  • 0.32.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade the Morelitea initiative platform to version 0.32.4 or later, which addresses this vulnerability by properly invalidating JWT tokens upon password changes. Until the upgrade is applied, administrators should consider implementing manual token revocation mechanisms if supported, such as maintaining a token blacklist or reducing token lifetimes to minimize exposure. Monitoring and logging of API access using JWTs should be enhanced to detect suspicious activity involving old tokens. Additionally, enforcing multi-factor authentication (MFA) can reduce the risk of token compromise. Security teams should review their incident response plans to include token revocation strategies and educate users about the importance of password changes and session management. Network-level protections, such as IP whitelisting and anomaly detection, can provide additional layers of defense. Finally, organizations should audit their deployment configurations to ensure secure storage and transmission of JWTs to prevent interception.

Description

Initiative is a self-hosted project management platform. Versions of the application prior to 0.32.4 do not invalidate previously issued JWT access tokens after a user changes their password. As a result, older tokens remain valid until expiration and can still be used to access protected API endpoints. This behavior allows continued authenticated access even after the account password has been updated. Version 0.32.4 fixes the issue.

References

Community reviews

Loading reviews…