CVE-2026-21653 CCure 9000 and victor application server vulnerability
Victor SSRF vulnerability in Johnson Controls CCure 9000 and victor application server allows Server Side Request Forgery. This issue affects CCure 9000 and victor application server: from 2.9 through 3.0.
Browse SSRF security risksQuick answer
Johnson Controls CCure 9000 and victor application server should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- <= 3.0
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-21653 affects CCure 9000 and victor application server and involves server-side request forgery. Successful exploitation may make the server contact internal services or expose data that should not be reachable externally. Prioritize internet-facing, privileged, automation, and production deployments. No confirmed fixed version is recorded for CVE-2026-21653; follow the linked vendor advisory, apply its mitigation, and update CCure 9000 and victor application server as soon as a supported patched release is available.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses CCure 9000 and victor application server.
- Compare the installed version with the recorded affected range: <= 3.0.
- No confirmed fixed version is recorded for CVE-2026-21653; follow the linked vendor advisory, apply its mitigation, and update CCure 9000 and victor application server as soon as a supported patched release is available.
- Until patched, restrict URL inputs and block outbound access to private, loopback, link-local, and cloud-metadata addresses.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to CCure 9000 and victor application server; remove access that is not required.
- Review proxy, DNS, firewall, cloud-metadata, and application logs for requests to internal, loopback, link-local, or unusual external addresses.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-21653 in place.
- Use a safe regression test to confirm the affected server-side request forgery path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-21653?
Johnson Controls CCure 9000 and victor application server versions listed as affected should be reviewed: <= 3.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.