Cyber Resilience

CVE-2026-25099

Bludit ≤ 3.18.4

Published
27 March 2026
Modified
01 April 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.019 78th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2026-25099 is a high-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Bludit Bludit. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 22% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Bludit’s API plugin is affected by an unrestricted file upload vulnerability tracked as CVE-2026-25099. An authenticated user possessing a valid API token can upload files with arbitrary extensions and content types that are subsequently stored on the server and can be executed, resulting in remote code execution. The flaw is classified under CWE-434 and carries a CVSS 4.0 score of 8.7. It was addressed in Bludit version 3.18.4.

An attacker who obtains a legitimate API token can exploit the issue over the network without user interaction to place and run malicious files, achieving full control over the affected Bludit instance including the ability to modify, exfiltrate, or disrupt data and services.

The official fix is available in the 3.18.4 release notes on GitHub, and further details are provided in the CERT.pl advisory at the referenced URL. Operators should upgrade promptly and review API token issuance practices.

EPSS for the CVE rose from a low baseline to a peak of 0.0142 before settling at the current value of 0.0053, indicating emerging exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Bludit’s API plugin allows an authenticated attacker with a valid API token to upload files of any type and extension without restriction, which can then be executed, leading to Remote Code Execution. This issue was fixed in 3.18.4.

CWE(s)
CWE-434

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
attack.mitre.org →
T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1105 Ingress Tool Transfer Command And Control
Adversaries may transfer tools or other files from an external system into a compromised environment.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-34845Same product: Bludit Bludit
CVE-2024-24550Same product: Bludit Bludit
CVE-2024-24551Same product: Bludit Bludit
CVE-2023-53907Same product: Bludit Bludit
CVE-2026-27741Same product: Bludit Bludit
CVE-2019-16113Same product: Bludit Bludit
CVE-2024-24554Same product: Bludit Bludit
CVE-2026-25100Same product: Bludit Bludit
CVE-2026-27742Same product: Bludit Bludit
CVE-2024-25297Same product: Bludit Bludit

Affected Assets

bludit
bludit
≤ 3.18.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

SI-3 Malicious Code Protection good match

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

CM-7 Least Functionality partial match

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-18 Mobile Code partial match

Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-05 mostly match
prevents

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-06 partial match
prevents

Secure development practices include input validation and file-type restrictions that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.

A.8.30 Outsourced development partial match
prevents

Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.

A.8.7 Protection against malware partial match
mitigates

Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.

References