Skip to content

Instantly share code, notes, and snippets.

@alon710
Created January 28, 2026 11:40
Show Gist options
  • Select an option

  • Save alon710/c6b62126b0e7801216cc693127d0bc7b to your computer and use it in GitHub Desktop.

Select an option

Save alon710/c6b62126b0e7801216cc693127d0bc7b to your computer and use it in GitHub Desktop.
GHSA-528q-4pgm-wvg2: Echo Chamber of Doom: Reflected XSS in go-httpbin - CVE Security Report

GHSA-528q-4pgm-wvg2: Echo Chamber of Doom: Reflected XSS in go-httpbin

CVSS Score: 6.1 Published: 2026-01-02 Full Report: https://cvereports.com/reports/GHSA-528q-4pgm-wvg2

Summary

A classic tale of a feature becoming a bug. The popular debugging tool go-httpbin allowed users to control both the reflected content and the Content-Type header, creating a trivial path to Cross-Site Scripting (XSS).

TL;DR

go-httpbin < 2.18.0 contains a Reflected XSS vulnerability. By manipulating the 'Content-Type' query parameter on specific endpoints, attackers can force the server to render arbitrary JSON or Base64 input as HTML, executing malicious JavaScript in the victim's browser.

Exploit Status: POC

Technical Details

  • GHSA ID: GHSA-528q-4pgm-wvg2
  • CVSS: 6.1 (Medium)
  • CWE: CWE-79 (XSS)
  • Attack Vector: Network
  • Privileges Required: None
  • User Interaction: Required (Phishing)

Affected Systems

  • go-httpbin < 2.18.0
  • go-httpbin: < 2.18.0 (Fixed in: 2.18.0)

Mitigation

  • Upgrade go-httpbin to version 2.18.0+
  • Audit environment variables to ensure UNSAFE_ALLOW_DANGEROUS_RESPONSES is false
  • Implement strict Content-Security-Policy (CSP) headers
  • Deploy behind a WAF with XSS filtering rules

Remediation Steps:

  1. Check the running version of go-httpbin.
  2. Pull the latest container image: docker pull mccutchen/go-httpbin:v2.18.0.
  3. Redeploy the service.
  4. Verify the fix by attempting the PoC URLs; the response should now be escaped or blocked.

References


Generated by CVEReports - Automated Vulnerability Intelligence

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment