Server-Side Request Forgery (SSRF)
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 27 Oct 2026, 00:28 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhalo-dev/halopkg:github/halo-dev/haloOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict access to the vulnerable endpoint to trusted users only and monitor for suspicious activity related to internal resource scanning attempts.
Description
A Server-Side Request Forgery (SSRF) vulnerability exists in the /themes/{name}/upgrade-from-uri endpoint of halo version 2.22.14. This flaw allows authenticated attackers to send crafted GET requests that can scan internal resources. The vulnerability has a CVSS 3.1 base score of 6.5, indicating medium severity. No public exploits or known active exploitation have been reported. No patch or remediation information is currently provided.