CVE-2026-43644

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-43644 has a CVSS score of 5.4 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.1-0.20260519111337-cbebb20fd485); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-43644? CVE-2026-43644 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/stefanprodan/podinfo (go), affecting versions < 1.8.1-0.20260519111337-cbebb20fd485. It is fixed in 1.8.1-0.20260519111337-cbebb20fd485. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-43644? CVE-2026-43644 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/stefanprodan/podinfo are affected by CVE-2026-43644? github.com/stefanprodan/podinfo (go) versions < 1.8.1-0.20260519111337-cbebb20fd485 is affected.
4. Is there a fix for CVE-2026-43644? Yes. CVE-2026-43644 is fixed in 1.8.1-0.20260519111337-cbebb20fd485. Upgrade to this version or later.
5. Is CVE-2026-43644 exploitable, and should I be worried? Whether CVE-2026-43644 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-43644 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-43644? Upgrade github.com/stefanprodan/podinfo to 1.8.1-0.20260519111337-cbebb20fd485 or later.