CISA Warns: Johnson Controls C-CURE 9000 Security Platform Under Active Exploitation (CVE-2026-21655)

Johnson Controls' C-CURE 9000 and Victor application server platforms — which manage access control, video surveillance, and physical security across thousands of commercial and industrial facilities worldwide — have been hit with a CISA advisory (ICSA-26-204-01) identifying a critical vulnerability that allows unauthenticated remote code execution on adjacent networks.

CVE-2026-21655 is a deserialization of untrusted data flaw in the Victor application (affecting versions up to v2.90/v3.0) on Windows. Under certain conditions, an attacker on the same network segment can exploit a vulnerable deserialization path (LV1.1) to execute arbitrary code on the C-CURE 9000 or Victor server, as well as on connected workstations used by physical security personnel. The vulnerability carries a CVSS v3 score of 9.6 — classified as Critical — and has already been added to CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild.

A companion vulnerability, CVE-2026-21653, is a Server-Side Request Forgery (SSRF) flaw in the Victor web component (versions up to v7.1) that enables a high-privilege attacker to cause the server to initiate unexpected network connections to internal resources. OffSeq's Threat Radar analysis notes the CVSS 4.0 vector shows a network attack path with low complexity, partial privileges required, and high impact on confidentiality and integrity.

U.S. flag
Source image 1

Johnson Controls has released a fix in C-CURE 9000 / Victor version 3.20 and later. Until organizations upgrade, the vendor recommends network segmentation: isolate C-CURE 9000 and Victor application servers on a dedicated segment and restrict access to port 8999 to only authorized systems.

For

Source article image
Source image 2
building management and physical security teams, this is a high-priority patch. C-CURE 9000 and Victor are deployed across airports, data centers, government facilities, and manufacturing plants — making the RCE path especially dangerous for organizations that rely on these platforms for both digital and physical perimeter defense.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more