How to Fix CVE-2026-36757: n/a (Bundle Sibling)
By Sai Kiran Pandrala
Last verified: 2026-05-25
CVE-2026-36757 is a sibling vulnerability in the same vendor advisory as CVE-2026-36756. Applying the patched build named in the primary write-up closes this CVE as well.
| Severity | CVSS 4.3 - Medium |
|---|---|
| Actively exploited? | Not currently in CISA KEV |
| Affected | Same as the bundle - see CVE-2026-36756 |
| Fixed in | Same patched build as CVE-2026-36756 (See vendor advisory) |
| Type (CWE) | n/a |
What's different about CVE-2026-36757?
A Server-Side Request Forgery (SSRF) in the /plugins/{name}/upgrade-from-uri endpoint of halo v2.22.14 allows authenticated attackers to scan internal resources via a crafted GET request.
The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.
How to fix CVE-2026-36757
Apply the patched build per the primary write-up: How to Fix CVE-2026-36756.
The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.
Frequently asked questions
Is CVE-2026-36757 fixed by the same patch as CVE-2026-36756?
Yes. CVE-2026-36757 ships in the same vendor advisory as CVE-2026-36756. Applying the patched build named in the primary write-up closes both.
What is the CVSS score for CVE-2026-36757?
The CVSS base score is 4.3 (Medium).
Is it being exploited?
It is not currently listed in CISA KEV.
References
- Official vendor advisory: https://github.com/halo-dev/halo
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-36757
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-36756
*Part of the n/a bundle. Full procedure at CVE-2026-36756.*