Skip to main content

GoFound EUVDEUVD-2026-115204

| CVE-2026-120444 HIGH
Path Traversal (CWE-22)
2026-11-02 VulnCheck GHSA-wpw5-72j3-wj9h
7.2
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed GoFound API (direct or via victim browser)
  2. Exploit
    Craft GET to /api/db/drop with ../ in database param
  3. Execution
    Path traversal escapes data directory
  4. Impact
    os.RemoveAll deletes arbitrary directories

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

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

Exploitation Conditions

Exploitation requires network reachability to the GoFound HTTP API endpoints /api/db/create and /api/db/drop, which per the description accept unauthenticated GET requests; the attacker supplies ../ sequences in the 'database' parameter to escape the data directory and trigger os.RemoveAll on arbitrary directories. The direct attack needs no authentication and no special configuration against instances through version 1.4.1. The main limiting factor is exposure: the API must be reachable by the attacker, or - for the browser-delivered (CSRF-style) variant captured by the assigned UI:P metric - a victim's browser must be able to reach the target instance. No specific non-default feature toggle is named in the sources; the trigger is the traversal payload in the database parameter.

Impact

The assigned CVSS 4.0 vector (7.2, High) reports AV:N/AC:L/PR:N, meaning a network-reachable, low-complexity, unauthenticated attack, with impact confined to integrity and availability of the vulnerable system (VI:H/VA:H, VC:N) - consistent with arbitrary directory deletion via os.RemoveAll and no data-confidentiality exposure. There is a notable conflict in the interaction metric: the assigned vector uses UI:P (passive user interaction, reflecting the 'via a victim's browser' CSRF-style path), yet the description explicitly states the GET requests can be sent 'directly,' which implies no user interaction is required for server-exposed instances - verify the intended trigger model with the reporter, as the direct path raises real risk above the 7.2 rating. On decision signals: this is NOT in CISA KEV, there is no confirmed active exploitation, EPSS was not provided in the input, and the only exploit artifact is an unverified PoC reference. The vuln.today priority is 'this_week,' indicating a moderate-high but non-emergency urgency. Netting these out: the flaw is genuinely dangerous where the GoFound HTTP API is network-exposed (unauthenticated, trivial to trigger, destructive), but the absence of KEV/EPSS and the niche footprint of GoFound suggest this is a credible priority for the small population that runs it rather than a widespread emergency. Treat exposed instances as high priority and internet-reachability as the dominant risk driver.

Exploit ScenarioDerived

An attacker who can reach a GoFound instance's HTTP API sends a GET request to /api/db/drop (or /api/db/create) with a database parameter containing ../ sequences, causing os.RemoveAll to delete directories outside the intended data directory. Because the endpoints are unauthenticated and accept GET, the same request can also be delivered through a victim's browser (CSRF-style) to reach instances the attacker cannot address directly. A public PoC reference exists; it is not verified as working exploit code.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Nov 02, 2026

Unauthenticated path traversal in GoFound through 1.4.1 allows remote attackers to delete arbitrary directories by supplying ../ sequences in the 'database' parameter of GET requests to /api/db/create and /api/db/drop, which reaches os.RemoveAll with an attacker-controlled path. The assigned CVSS 4.0 vector (7.2, High) rates it AV:N/AC:L/PR:N, so a network-reachable instance is directly attackable without credentials; because the endpoints accept GET, the same action can also be triggered from a victim's browser, which is what the UI:P metric captures. There is no KEV entry indicating active exploitation, and the available exploit reference is a public PoC write-up that has not been verified as working exploit code; no EPSS score was supplied, and the vuln.today decision label is 'this_week'.

RemediationAI

No fixed release version is listed in the available references - the upstream issue at https://github.com/sea-team/gofound/issues/101 and the VulnCheck advisory at https://www.vulncheck.com/advisories/gofound-through-1.4.1-path-traversal-via-database-parameter-in-api-db-drop are the tracking points, so check them for a patched tag and upgrade as soon as one is published; until then treat 1.4.1 and earlier as affected. Because the endpoints are unauthenticated by design in this version, the most reliable compensating control is exposure reduction: firewall or bind the GoFound HTTP API so only trusted hosts can reach it, and place it behind a reverse proxy that enforces authentication on /api/db/* paths - the trade-off is that any legitimate unauthenticated client of those endpoints will break. If the drop and create endpoints are not used in your deployment, block them entirely at the proxy (return 403 for /api/db/create and /api/db/drop), accepting that database lifecycle operations must then be performed another way. For the browser-delivered variant (UI:P), rejecting cross-origin requests with strict Origin/Referer checks or a CSRF token on state-changing GETs reduces drive-by triggering, but does nothing against a direct attacker, and proxy-side filtering of ../ sequences in the database parameter should be treated as a heuristic that alternative encodings can bypass rather than as a fix. Back up the data directory and its parent paths so that an accidental or malicious os.RemoveAll call is recoverable.

Affected VersionsENISA

GoFound 0 ≤1.4.1

Affected Packages

euvd gofound no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

GoFound is an open-source full-text search engine written in Go (module path sea-team/gofound), and this is a classic CWE-22 improper limitation of a pathname to a restricted directory. The HTTP handlers behind /api/db/create and /api/db/drop take the 'database' request parameter and use it to build a filesystem path under the configured data directory; when the value contains ../ sequences it is not canonicalized or confined before being handed to Go's os.RemoveAll, so the recursive delete escapes the data root and removes whatever directory the path resolves to. The advisory references searcher/container.go and searcher/engine.go at tag v1.4.1 as the source locations involved in this path handling. The impact profile is integrity and availability only (VI:H/VA:H, VC:N) - destructive deletion rather than data disclosure - and the trigger is the traversal payload in the database parameter; no special configuration or non-default feature toggle is named in the sources.

Know when Gofound gets its next vulnerability

  • 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

Vendor (VulnCheck) PRIMARY 7.2 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 9.1 CRITICAL

Unauthenticated network GET to the API (AV:N/AC:L/PR:N) with direct exploitation possible so UI:N; arbitrary directory deletion yields I:H/A:H and no confidentiality impact (C:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

GoFound through 1.4.1 contains a path traversal vulnerability that allows unauthenticated attackers to delete arbitrary directories by supplying ../ sequences in the database parameter. Attackers can send GET requests to /api/db/create and /api/db/drop, directly or via a victim's browser, triggering os.RemoveAll on directories outside the data directory.

Technical POC Analysis

CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, "path traversal").

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

CVE-2026-120444 is a high-severity vulnerability in GoFound (a search engine) that allows an unauthenticated remote attacker to delete arbitrary directories on the server. Any internet-facing or internal GoFound instance up to version 1.4.1 is at risk, potentially leading to data loss, service disruption, and follow-on compromise. Leadership should prioritize remediation this week, as a public exploit reference exists and the vulnerability is trivial to exploit.

Business Impact: High
Compensating Controls

Restrict network access to GoFound instances to trusted IPs, enforce authentication at a reverse proxy, run GoFound with minimal filesystem privileges (non-root, read-only mounts for critical directories), and monitor logs for path traversal attempts.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
niche open-source Go search engine, limited enterprise deployment footprint
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

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 HIGH
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

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