podinfo: cross-site scripting vulnerability in the /echo and /api/echo endpoints

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

• CVE-2026-43644: 0.19% estimated exploitation activity in the next 30 days; percentile 9.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

podinfo through 6.11.2 contains a reflected cross-site scripting vulnerability in the /echo and /api/echo endpoints where the echoHandler writes request body content directly to the response without setting explicit Content-Type or X-Content-Type-Options headers. Attackers can craft cross-origin HTML pages with auto-submitting forms containing script payloads in the request body, which are served as text/html due to Go's content type detection, allowing the reflected script to execute in the podinfo origin context when victims visit the attacker's page.

Published by the source

14 May 2026, 15:31 UTC

Last modified by the source

20 May 2026, 15:48 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q23m-vm9r-5745

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

# Patch Next advisory brief: CVE-2026-43644

Advisory: podinfo: cross-site scripting vulnerability in the /echo and /api/echo endpoints
IDs: CVE-2026-43644, GHSA-q23m-vm9r-5745
Record: https://patchnext.com/advisories/cve-2026-43644 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/stefanprodan/podinfo 1.8.1-0.20260519111337-cbebb20fd485. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/stefanprodan/podinfo: affected < 1.8.1-0.20260519111337-cbebb20fd485; fixed in 1.8.1-0.20260519111337-cbebb20fd485

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/stefanprodan/podinfo.
- 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-q23m-vm9r-5745 (GitHub-reviewed advisory GHSA-q23m-vm9r-5745 lists affected ranges: Go github.com/stefanprodan/podinfo >=0 <1.8.1-0.20260519111337-cbebb20fd485)

Commands are suggestions: review each one before running it.