Home
» Security vulnerabilities
» CVE-2026-2701
Authenticated user can upload a malicious file to the server and execute it, which leads to remote code execution.
NVD Status： Analyzed ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2026-2701
Conclusion & alert: CVE-2026-2701 is rated High Risk (76/100) : CVSS Critical severity, with high exploitation likelihood (EPSS 48.81%, 99th percentile).Core evidence: EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +47.64% over the last day, indicating growing attacker interest.Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2026-2701
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
1.17%
48.81%
+47.64%
2
2026-06-09
1.01%
1.17%
+0.16%
3
2026-05-28
—
1.01%
—
Full EPSS history
(13 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2026-2701
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
9.1
3.1
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.3
6.0
[email protected]
8.8
3.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8
5.9
[email protected]
Weakness enumeration for CVE-2026-2701
GitHub Security Advisory for CVE-2026-2701
GHSA-2vxx-w4h2-4g8g · Severity: critical
— Authenticated user can upload a malicious file to the server and execute it, which leads to...
Affected software / configurations for CVE-2026-2701
References for CVE-2026-2701
cvelogic
Threat Intelligence