WrenSecurity Fixes CREST _mimeType Cross-Site Scripting
Tech GuruQuick Answer
The CREST HTTP binding can produce executable HTML through the _mimeType parameter when a user follows an attacker-controlled link. Upgrade the affected dependencies, test security boundaries and retain deployed-version evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Record wrensec-commons dependencies, CREST endpoints, content-type negotiation and callers that use _mimeType. Match the documented versions, enabled features and attack prerequisites to the deployment before assigning applicability. Upgrade to 22.6.2 or 23.0.0. Until then, disallow _mimeType in both query strings and application/x-www-form-urlencoded bodies as the project recommends. Confirm deployed dependencies, response content types and rejection of disallowed MIME overrides; retain build and request-validation evidence.
Last verified: 2026-11-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | wrensec-commons CREST HTTP binding |
|---|---|
| Advisory | GHSA-4vhv-49g2-496q |
| CVE | CVE-2026-2102 |
| Authoritative release date | 2026-11-02 15:03:40 UTC |
| Authority revision date | No separate later revision date is displayed in the captured project advisories. |
| Affected versions | Issue-specific package ranges and configurations listed below; confirm feature use before assigning applicability. |
| Fixed version | wrensec-commons 22.6.2 or 23.0.0 |
| CVSS base score | 6.1 (CVSS v3.1) |
| CVSS severity | Moderate |
| Exploitation status | The cited authority does not state that this issue is being maliciously exploited.; no exploitation claim is inferred. |
Authority-Specific Scope And Version Evidence
| GHSA-4vhv-49g2-496q / CVE-2026-2102 | wrensec-commons: affected < 22.6.2,>= 23.0.0-M1,< 23.0.0 Patched versions 22.6.2,23.0.0. CVSS v3.1 6.1; Moderate. Published 2026-11-02T15:03:40Z. |
|---|
What Changed
The CREST HTTP binding can produce executable HTML through the _mimeType parameter when a user follows an attacker-controlled link.
What To Validate Now
- Inventory. Record wrensec-commons dependencies, CREST endpoints, content-type negotiation and callers that use _mimeType.
- Establish applicability. Match the documented versions, enabled features and attack prerequisites to the deployment before assigning applicability.
- Remediate. Upgrade to 22.6.2 or 23.0.0. Until then, disallow _mimeType in both query strings and application/x-www-form-urlencoded bodies as the project recommends.
- Validate. Confirm deployed dependencies, response content types and rejection of disallowed MIME overrides; retain build and request-validation evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
The attack requires user interaction. Apply parameter filtering to both supported input locations and test legitimate clients.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
