# CVE-2026-2102: XSS in wrensec-commons CREST framework HTTP binding via _mimeType parameter

Status: published. Published: 2026-11-02. Updated: 2026-11-02.

wrensec-commons contains a reflected cross-site scripting (XSS) vulnerability in the CREST framework's HTTP binding. The HttpUtils.prepareResponse() method used the _mimeType request parameter to set the Content-Type response header without proper sanitization. By sending a GET request with _mimeType=text/html, an attacker could cause the browser to interpret a CREST JSON response as HTML, enabling execution of arbitrary JavaScript in the victim's browser. The vulnerability is exploitable by tricking a user into visiting a crafted URL targeting any deployed CREST endpoint. The issue is fixed in versions 22.6.2 and 23.0.0.

## Remediation

- workaround: Disallow the _mimeType request parameter in both query string and x-www-form-urlencoded request bodies. (source: CNA: WrenSecurity)
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: WrenSecurity) — https://github.com/WrenSecurity/wrensec-commons/commit/65bbfd8c63c42e84ff7699aa5b82a22c08a12624
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: WrenSecurity) — https://github.com/WrenSecurity/wrensec-commons/commit/5b50c64c14943b6f4d7faf996345e603956bae1d

## Affected products and versions

- Wren Security / wrensec-commons (org.wrensecurity.commons:json-resource-http): ≥ 0; < 22.6.2 (affected, semver); ≥ 23.0.0-M1; < 23.0.0 (affected, semver). Source: CNA: WrenSecurity

## Severity and prioritization

- CVSS 3.1: 6.1 (medium); CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N; source: CNA: WrenSecurity

- CVSS 3.1: 6.1 (medium); CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N; source: NVD: b6ef82d7-f637-461b-aedd-74f5857d5f5b

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-79

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/WrenSecurity/wrensec-commons/security/advisories/GHSA-4vhv-49g2-496q (CNA: WrenSecurity; third-party-advisory)

- https://github.com/WrenSecurity/wrensec-commons/commit/65bbfd8c63c42e84ff7699aa5b82a22c08a12624 (CNA: WrenSecurity; patch)

- https://github.com/WrenSecurity/wrensec-commons/commit/5b50c64c14943b6f4d7faf996345e603956bae1d (CNA: WrenSecurity; patch)

- https://github.com/WrenSecurity/wrensec-commons/commit/5b50c64c14943b6f4d7faf996345e603956bae1d (b6ef82d7-f637-461b-aedd-74f5857d5f5b)

- https://github.com/WrenSecurity/wrensec-commons/commit/65bbfd8c63c42e84ff7699aa5b82a22c08a12624 (b6ef82d7-f637-461b-aedd-74f5857d5f5b)

- https://github.com/WrenSecurity/wrensec-commons/security/advisories/GHSA-4vhv-49g2-496q (b6ef82d7-f637-461b-aedd-74f5857d5f5b)

## Provenance

- CNA: WrenSecurity: https://www.cve.org/CVERecord?id=CVE-2026-2102; retrieved 2026-11-02; source updated 2026-11-02

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2102; retrieved 2026-11-02; source updated 2026-11-02

Revision: fe153fb5f73a99e1dc160a33be1d81ac561829cb32653385497d00f50e47507f

Canonical: https://y2.dev/cve/CVE-2026-2102

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.