Categories
CVE-2025-45286

Cross-Site Scripting (XSS) in github.com/mccutchen/go-httpbin (CVE-2025-45286)

Summary

Cross-site scripting in github.com/mccutchen/go-httpbin (CVE-2025-45286). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.18.0 or later.

Original description

The description as published by the source.

Description

The go-httpbin framework is vulnerable to XSS as the user can control the Response Content-Type from GET parameter. This allows attacker to execute cross site scripts in victims browser.

Affected URLs:

  • /response-headers?Content-Type=text/html&xss=%3Cimg/src/onerror=alert(%27xss%27)%3E
  • /base64/PGltZy9zcmMvb25lcnJvcj1hbGVydCgneHNzJyk+?content-type=text/html
  • /base64/decode/PGltZy9zcmMvb25lcnJvcj1hbGVydCgneHNzJyk+?content-type=text/html

Steps to reproduce:

  1. Visit one of the above mentioned URLs.
  2. XSS window will popup

Suggested fix

  • Allow Only Safe Content-Type Values Or give users option to define whitelisted Content-Type headers

Criticality

The following can be major impacts of the issue:

  • Access to victim's sensitive Personal Identifiable Information.
  • Access to CSRF token
  • Cookie injection
  • Phishing
  • And any other thing Javascript can perform

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-45286 has been found in github.com/mccutchen/go-httpbin.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/mccutchen/go-httpbin to 2.18.0 or later.
If unsure, ask your IT team or search "github.com/mccutchen/go-httpbin CVE-2025-45286" on the vendor's site.

CVE-2025-45286 (github.com/mccutchen/go-httpbin) — CWE-79
Patched: 2.18.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in github.com/mccutchen/go-httpbin.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/mccutchen/go-httpbin.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.18.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/mccutchen/go-httpbin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/mccutchen/go-httpbin' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/mccutchen/go-httpbin を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/mccutchen/go-httpbin to 2.18.0

    ステージング環境で 2.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/mccutchen/go-httpbin
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.18.0"}]}]
Go github.com/mccutchen/go-httpbin/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.18.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details