HTTP Header Injection via Webhook API in Multiple WSO2 Products Allows Response Header Manipulation
Published May 11, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
HTTP Header Injection via Webhook API in Multiple WSO2 Products Allows Response Header Manipulation
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
In Webhook API invocations, the component accepts user-supplied input for HTTP request headers without sufficient validation or sanitization, allowing these headers to be injected into HTTP responses.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published May 11, 2026 · Last refreshed Nov 3, 2026