# CVE-2026-116647: Tanium addressed an improper output sanitization vulnerability in Comply.

Status: published. Published: 2026-10-27. Updated: 2026-11-04.

Tanium addressed an improper output sanitization vulnerability in Comply.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Tanium / Comply: ≥ 2.32; < 2.32.263 (affected, custom); ≥ 2.35; < 2.35.323 (affected, custom); ≥ 2.37; < 2.37.326 (affected, custom). Source: CNA: Tanium

## Severity and prioritization

- CVSS 3.1: 7.1 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L; source: CNA: Tanium

- CISA KEV: No listing in collected sources

- EPSS: 0.24% as of 2026-11-04; percentile 15.57%

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

- Weaknesses: CWE-1236

## Exploit evidence

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

## References

- https://security.tanium.com/TAN-2026-069 (CNA: Tanium)

## Provenance

- CNA: Tanium: https://www.cve.org/CVERecord?id=CVE-2026-116647; retrieved 2026-11-04; source updated 2026-11-04

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-116647; retrieved 2026-11-04; source updated Not reported

Revision: b3d030a132f2463ecb0b83cf5f0f800ed518d8c148c13dcfdcf5a3033fbb7db3

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

## 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.