Quick answers
- Is CVE-2026-40242 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40242 being exploited in the wild.
- How severe is CVE-2026-40242?
- High severity, with a CVSS score of 7.2, published 10 April 2026.
- Which products and versions are affected?
- Arcane backend <= 1.17.2; github.com/getarcaneapp/arcane/backend (Go) <= 1.17.2, SEMVER:introduced=0,fixed=1.17.3.
- Is there a fix for CVE-2026-40242?
- Yes. github.com/getarcaneapp/arcane/backend (Go): upgrade to 1.17.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40242 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-40242?
- Check whether you run Arcane backend, Getarcane Arcane or github.com/getarcaneapp/arcane/backend (Go) 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
- github.com/getarcaneapp/arcane/backend (Go): upgrade to 1.17.3 or later
go get github.com/getarcaneapp/arcane/backend@v1.17.3
Technical details
An unauthenticated SSRF vulnerability exists in the /api/templates/fetch endpoint of Arcane due to a lack of validation on the user-supplied 'url' parameter. The application performs a GET request to the provided URL without verifying the scheme, host, or destination CIDR. The vulnerability allows for conditional response reflection: valid JSON responses are reflected, while non-JSON responses or connection errors leak specific error messages (e.g., first-byte leaks or TCP timeouts). This can be exploited to perform internal port scanning and access internal-only HTTP services like Kubernetes APIs or metadata endpoints. The issue is fixed in version 1.17.3.
Affected products
- getarcaneapp Arcane backend <= 1.17.2
Identifiers
- CVE-2026-40242
- GHSA-ff24-4prj-gpmj
- GO-2026-5356
Timeline
- 2026-04-10: disclosed
- 2026-04-10: advisory
- 2026-04-10: patched: Fixed in version 1.17.3