Skip to main content
Mallory
MediumVulnerability

CVE-2026-25101: Session Fixation in Bludit

Published Mar 27, 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.
CVSS4.8Medium · v4
EPSS0.38%32nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Bludit
IdentifiersCVE-2026-25101CWE-384 · Session Fixation

Bludit contains a session fixation vulnerability in which a user's session identifier can be established prior to authentication and is not regenerated after successful login. Because the application accepts a pre-authentication session ID and preserves that same identifier across the authentication boundary, an attacker can set or predict a session value for a victim and then reuse it after the victim authenticates. This weakness affects Bludit versions before 3.17.2 and enables subsequent hijacking of the victim's authenticated session.

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 hijack a victim's authenticated Bludit session. Depending on the victim account's privileges, this can provide unauthorized access to the administrative interface or other authenticated functionality, enabling actions as that user, including content management and administrative operations available to the compromised account.

Mitigation

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

If immediate upgrade is not possible, reduce exposure by enforcing reauthentication for sensitive actions, shortening session lifetimes, invalidating existing sessions, and monitoring for anomalous session reuse. Deploy controls that prevent attacker-controlled session identifiers from being accepted across login boundaries, such as regenerating server-side sessions after authentication via local patching or compensating controls in the application stack where feasible. User awareness and anti-phishing measures may also reduce the likelihood of an attacker successfully fixing a session ID for a victim.

Remediation

Patch, then assume compromise.

Upgrade Bludit to version 3.17.2 or later, which fixes the issue. The remediation is to ensure session identifiers are regenerated upon successful authentication so that any session ID established before login cannot be reused as an authenticated session.

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
BluditBluditapplication
FAQ

Frequently asked questions

Is CVE-2026-25101 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-25101 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-25101?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-25101.
Is there a patch for CVE-2026-25101?
Upgrade Bludit to version 3.17.2 or later, which fixes the issue. The remediation is to ensure session identifiers are regenerated upon successful authentication so that any session ID established before login cannot be reused as an authenticated session.
What products are affected by CVE-2026-25101?
Bludit.
How severe is CVE-2026-25101?
CVE-2026-25101 has a CVSS v4 score of 4.8 (Medium) and an EPSS score of 0.38% (32nd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 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 activity2Community discussion across Reddit, Mastodon, and other social sources.