CVE-2025-70950
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in gohttp commit 34ea51 allows attackers to execute a directory traversal via supplying a crafted request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe gohttp library in commit 34ea51 contains a directory traversal vulnerability that allows attackers to access files outside the intended web root directory by supplying crafted requests containing path traversal sequences (such as '../'). This occurs due to insufficient input validation on file paths in the HTTP request handling.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify gohttp in your dependenciesReview your project's go.mod file or vendor directory for the gohttp library import, and check any dependency management tooling (go list, vendor listing, etc.)Affected if gohttp is present as a direct or indirect dependency
-
Locate the installed gohttp versionRun 'go list -m all' or check the gohttp module cache to find the exact commit hash or version tag currently in useAffected if The installed version corresponds to commit 34ea51 or an earlier commit without the path traversal fix
-
Inspect HTTP handler code for path handlingSearch the gohttp source code in your environment for file serving functions and examine how request paths are processed (look for filepath.Join, os.Open, or similar file operations without prior sanitization)Affected if The code directly uses request URL paths in file operations without validating or normalizing them
-
Check for path traversal protectionSearch the gohttp source code for path validation mechanisms such as filepath.Clean, strings.Contains checks for '../', or explicit path boundary enforcement before file accessAffected if No path traversal protection (filepath.Clean, '../' rejection) is found in the file serving code path
You are affected if gohttp is present in your environment AND the installed version is at or before commit 34ea51 without subsequent path traversal protection fixes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict path validation and sanitization to reject requests containing '..' sequences or absolute paths, or upgrade to a patched version of gohttp if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-70950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data