Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.3

gohttp is vulnerable to directory traversal via a crafted request

CVE-2025-70950GHSA-rg3p-p27c-2f39

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/itang/gohttp

    Affected
    <= 0.0.0-20170713062009-34ea516ae408
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
  • CVE-2025-70950: 0.52% estimated exploitation activity in the next 30 days; percentile 44.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

An issue in gohttp commit 34ea51 allows attackers to execute a directory traversal via supplying a crafted request.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-rg3p-p27c-2f39

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-70950

Advisory: gohttp is vulnerable to directory traversal via a crafted request
IDs: CVE-2025-70950, GHSA-rg3p-p27c-2f39
Record: https://patchnext.com/advisories/cve-2025-70950 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/itang/gohttp: affected <= 0.0.0-20170713062009-34ea516ae408

## Suggested inspection (read-only)
- Go github.com/itang/gohttp: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/itang/gohttp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rg3p-p27c-2f39 (GitHub-reviewed advisory GHSA-rg3p-p27c-2f39 lists affected ranges: Go github.com/itang/gohttp >=0 <=0.0.0-20170713062009-34ea516ae408)

Commands are suggestions: review each one before running it.

Loading voting…