GHSA-XMRV-PMRH-HHX2

CVSSv3.1 Rating: [Medium]
CVSSv3.1 Score: [5.9]
CVSSv3.1 Vector String: [CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H]

Summary and Impact

An issue exists in the the EventStream header decoder in AWS SDK for Go v2 in versions predating 2026-03-23. An actor can send a malformed EventStream response frame containing a crafted header value type byte outside the valid range, which can cause the host process to terminate.

Impacted versions: < 2026-03-23

Workarounds

Not Applicable

References

If you have any questions or comments about this advisory, we ask that you contact [AWS/Amazon] Security via our vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

GHSA-XMRV-PMRH-HHX2 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. 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.7.8, 1.15.2, 1.51.8, 1.50.4, 1.65.0, 1.52.19, 1.43.5, 1.88.5, 1.35.15, 1.97.3, 1.39.6, 1.34.5); upgrading removes the vulnerable code path.

Kodem intelligence

This issue has been addressed in versions 2026-03-23 and above. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

1. What is GHSA-XMRV-PMRH-HHX2? GHSA-XMRV-PMRH-HHX2 is a medium-severity improper input validation vulnerability in github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream (go), affecting versions < 1.7.8. It is fixed in 1.7.8, 1.15.2, 1.51.8, 1.50.4, 1.65.0, 1.52.19, 1.43.5, 1.88.5, 1.35.15, 1.97.3, 1.39.6, 1.34.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is GHSA-XMRV-PMRH-HHX2? GHSA-XMRV-PMRH-HHX2 has a CVSS score of 5.9 (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 packages are affected by GHSA-XMRV-PMRH-HHX2?
   • github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream (go) (versions < 1.7.8)
   • github.com/aws/aws-sdk-go-v2/service/bedrockagentcore (go) (versions < 1.15.2)
   • github.com/aws/aws-sdk-go-v2/service/bedrockagentruntime (go) (versions < 1.51.8)
   • github.com/aws/aws-sdk-go-v2/service/bedrockruntime (go) (versions < 1.50.4)
   • github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs (go) (versions < 1.65.0)
   • github.com/aws/aws-sdk-go-v2/service/iotsitewise (go) (versions < 1.52.19)
   • github.com/aws/aws-sdk-go-v2/service/kinesis (go) (versions < 1.43.5)
   • github.com/aws/aws-sdk-go-v2/service/lambda (go) (versions < 1.88.5)
   • github.com/aws/aws-sdk-go-v2/service/lexruntimev2 (go) (versions < 1.35.15)
   • github.com/aws/aws-sdk-go-v2/service/s3 (go) (versions < 1.97.3)
   • github.com/aws/aws-sdk-go-v2/service/sagemakerruntime (go) (versions < 1.39.6)
   • github.com/aws/aws-sdk-go-v2/service/transcribestreaming (go) (versions < 1.34.5)
4. Is there a fix for GHSA-XMRV-PMRH-HHX2? Yes. GHSA-XMRV-PMRH-HHX2 is fixed in 1.7.8, 1.15.2, 1.51.8, 1.50.4, 1.65.0, 1.52.19, 1.43.5, 1.88.5, 1.35.15, 1.97.3, 1.39.6, 1.34.5. Upgrade to this version or later.
5. Is GHSA-XMRV-PMRH-HHX2 exploitable, and should I be worried? Whether GHSA-XMRV-PMRH-HHX2 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 GHSA-XMRV-PMRH-HHX2 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 GHSA-XMRV-PMRH-HHX2?
   • Upgrade github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream to 1.7.8 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/bedrockagentcore to 1.15.2 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/bedrockagentruntime to 1.51.8 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/bedrockruntime to 1.50.4 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs to 1.65.0 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/iotsitewise to 1.52.19 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/kinesis to 1.43.5 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/lambda to 1.88.5 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/lexruntimev2 to 1.35.15 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/s3 to 1.97.3 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/sagemakerruntime to 1.39.6 or later
   • Upgrade github.com/aws/aws-sdk-go-v2/service/transcribestreaming to 1.34.5 or later