Quick answers
- Is CVE-2026-59670 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59670 being exploited in the wild.
- How severe is CVE-2026-59670?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- Repasat before April 2026 patch.
- Is there a fix for CVE-2026-59670?
- Yes: fixed in April patch version 20260402. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59670 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59670?
- Check whether you run Repasat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: April patch version 20260402
Technical details
Fifteen reflected XSS vulnerabilities exist across multiple parameters and endpoints in the Repasat application (CVE-2026-59659 through CVE-2026-59683). Each vulnerability involves insufficient input sanitization on parameters such as nomZonaGeo, nomTransportista, nomRuta, and others across various business entity endpoints. Exploitation requires an authenticated user and user interaction (clicking a crafted link), but allows execution of arbitrary JavaScript in the victim's browser context with the same privileges as the authenticated user.
Affected products
- Repasat Repasat before April 2026 patch
Timeline
- 2026-10-02: disclosed