Skip to main content

Suse CVE-2026-30955

| EUVDEUVD-2026-12077 MEDIUM
Uncontrolled Resource Consumption (CWE-400)
2026-03-13 https://github.com/Forceu/Gokapi GHSA-qwc6-vc2v-2ggj
6.5
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK

1 technique across 1 tactic: Impact

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

CVSS 6.5 with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H indicates moderate-to-high severity: the attack is remotely exploitable over the network (AV:N) with low complexity (AC:L), requires low privilege (authenticated user, PR:L), requires no user interaction (UI:N), is limited to availability impact (A:H, no confidentiality or integrity breach), and does not affect other systems (S:U). The requirement for authentication (PR:L) significantly reduces real-world attack surface compared to unauthenticated DoS vulnerabilities. However, in environments where user registration is open or internal users have malicious intent, the risk is elevated. The attack is deterministic and highly automatable (concurrent large payloads guarantee success). A patch is available (v2.2.4), indicating the vendor has acknowledged and fixed the issue. Without EPSS or KEV data in sources, we assess this as a legitimate but not critical priority: handle promptly in patching cycles, but not an emergency for defense-in-depth purposes. Organizations with strict authentication controls and small user bases face minimal real-world risk.

Exploit ScenarioDerived

An authenticated user (obtained via credential compromise, insider threat, or open registration) crafts a script to send multiple concurrent HTTP POST requests to a vulnerable Gokapi API endpoint (likely a file upload or data ingestion endpoint) with multi-gigabyte payloads. Each request is not rejected due to size constraints and triggers memory allocation in the server process. Within seconds to minutes, the Gokapi process consumes available system RAM, triggering an OOM killer (Linux oom-kill, Windows memory pressure), and the service abruptly crashes. All connected users lose access to the service. Recovery requires manual server restart. No POC is explicitly mentioned in the provided intelligence, but the attack is trivial to construct given the vulnerability's deterministic nature (curl/wget with large input file repeated in parallel). Attacker requires only a valid account and network access to the API endpoint.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 13, 2026

Denial-of-service vulnerability in Gokapi, a file-sharing server, wherein an authenticated attacker can send unbounded request bodies to an API endpoint without size restrictions, causing out-of-memory (OOM) conditions that crash the service and deny access to all users. The vulnerability requires valid authentication credentials but no special privileges, and is classified as high-severity (CVSS 6.5) due to guaranteed availability impact. Patch availability exists in version 2.2.4 and later.

RemediationAI

Upgrade Gokapi to version 2.2.4 or newer. Release is available at https://github.com/Forceu/Gokapi/releases/tag/v2.2.4; priority: High Workaround (Interim): If immediate patching is not feasible, implement reverse proxy or load balancer limits (nginx, HAProxy, etc.) to enforce maximum request body sizes on all endpoints (recommend 10-100 MB depending on use case). Example nginx: 'client_max_body_size 50M;'; priority: Medium Defense-in-Depth: Restrict API access via firewall/WAF to trusted networks or IP ranges. Limit concurrent connections per authenticated user. Monitor process memory usage and set OS-level ulimits.; priority: Medium

Affected VersionsENISA

Gokapi < 2.2.4

Affected Packages

go github.com/forceu/gokapi fix: 2.2.4
euvd gokapi fix: 2.2.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability affects the Go package github.com/Forceu/Gokapi (identified via CPE: pkg:go/github.com_forceu_gokapi), a file-sharing and temporary file hosting service written in Go. The root cause is classified under CWE-400 (Uncontrolled Resource Consumption / Denial of Service), specifically the absence of request body size limits on one or more API endpoints. When processing HTTP requests, the affected endpoint(s) lack MaxRequestBodySize or similar protections that would constrain memory allocation. An authenticated client sending large payloads triggers unbound memory allocation in the Go HTTP server, leading to OOM kill by the OS and complete service termination. This is a classic resource exhaustion flaw in HTTP API design.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
CVE Published
Mar 13, 2026 - 18:56 nvd
MEDIUM 6.5

DescriptionGitHub Advisory

Summary

An API endpoint accepts unbounded request bodies without any size limit. An authenticated user can cause an OOM kill and complete service disruption for all users.

Impact

Any authenticated user can crash the Gokapi server by sending concurrent large payloads.

Executive ViewAI

Why It Matters

CVE-2026-30955 presents notable security risk, a resource exhaustion vulnerability rated CVSS 6.5. Service availability could be impacted. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Moderate
Compensating Controls

Apply vendor patch. If patching is delayed: implement rate limiting and resource quotas.

Threat Intelligence Overview

EPSS Score
0.0%
Top 94% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Vendor StatusVendor

SUSE

Severity: Medium

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy