Medium exploit reference

CVE-2025-63914 — An issue was discovered in Cinnamon kotaemon 0.11.0. The _may_extract_zip function in…

An issue was discovered in Cinnamon kotaemon 0.11.0. The _may_extract_zip function in the \libs\ktem\ktem\index\file\ui.py file does not check the contents of uploaded ZIP files. Although the contents are extracted into a temporary folder that is cleared before each extraction, successfully uploading a ZIP bomb could still cause the server to consume excessive resources during decompression. Moreover, if no further files are uploaded afterward, the extracted data could occupy disk space and potentially render the system unavailable. Anyone with permission to upload files can carry out this attack.

Published Nov 24, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: mitre

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.4% (30-day exploitation probability)+4
Technical severity (medium)+3
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.36%

ahead of 28% of scored CVEs · Oct 15, 2026

Affects

Cinnamon

Kotaemon

CVSS base

6.5

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Cinnamon Kotaemon).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Cinnamon	Kotaemon	version 0.11.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.5	CVSS 3.1	Medium	2.8	3.6	134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
6.5	CVSS 3.1	Medium	—	—	CISA-ADP via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-409

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.36%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 6.5
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Nov 24, 2025 · mitre

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/WxDou/CVE-2025-63914
Exploit, Third Party Advisory, NIST National Vulnerability Database
github.com/Cinnamon/kotaemon
Product, NIST National Vulnerability Database

Elsewhere on this site

Cinnamon
every CVE for this vendor

CWE-409
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-82281 Kotaemon Missing Ownership Check in Conversation Functions Aug 28, 2026
Critical CVE-2026-69098 kotaemon 0.12.0 Unauthenticated Remote Code Execution via Insecure Deserialization Aug 4, 2026
Medium CVE-2025-56526 Cross-site Scripting (XSS) in Cinnamon Kotaemon Nov 18, 2025
High CVE-2025-56527 Plaintext password storage in Kotaemon 0.11.0 in the client's localStorage. Nov 18, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-63914 is "An issue was discovered in Cinnamon kotaemon 0.11.0. The _may_extract_zip function in…", rated Medium. It affects Kotaemon (Cinnamon); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.36% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.