Cloud Context is now ISO 27001 certified!
- Cyber Security
- News
Some vulnerabilities are being exploited within 48 hours. Is your patch management keeping up?

“We’ll get to it in the next maintenance window.”
It’s a reasonable approach to routine updates. But when a serious security vulnerability emerges, your patch management process needs room to move sooner.
The Australian Cyber Security Centre (ACSC) has issued a critical alert urging organisations to accelerate patching and reduce their exposure to attack.
If you’re unsure where your gaps are, talk to our team. We can help you work out what needs attention.
In its alert published on the 17th of November 2026, the ACSC reported that publicly disclosed software vulnerabilities increased by 30% last financial year.
It also observed some vulnerabilities being successfully exploited within 48 hours of patches or mitigation advice becoming available. Automated and AI-enabled tools are helping attackers find and exploit weaknesses faster.
That doesn’t give every update the same deadline. It does mean a regular update schedule needs an urgent response process alongside it.
Make sure someone is responsible for reviewing security alerts, identifying affected systems and approving urgent action. Enable automatic updates where appropriate, and confirm your suppliers can promptly patch the systems they manage.
Review internet-facing systems and services, including remote access tools and network devices. Prioritise vulnerabilities based on their severity, evidence of exploitation and your exposure. Remove unnecessary external access.
Deploying an update and successfully applying it aren’t always the same thing. Check for failed installations, outstanding restarts and devices that missed deployment. Confirm the fix has taken effect.
Review unsupported systems, strengthen access controls and multi-factor authentication, and monitor for suspicious activity. Patching matters, but it works alongside these other protections.
Compatibility issues, business-critical applications and supplier dependencies can complicate updates. They still need a response.
The ACSC’s message is patch, protect, prevent. When patching has to wait, assess the risk, restrict exposure and apply temporary security controls while monitoring for suspicious activity.
Depending on the vulnerability, vendor guidance may include disabling an affected feature or limiting access to a service.
Give that temporary workaround an owner and a deadline for review, so it doesn’t quietly become permanent.
If a critical vulnerability affecting us was announced today, who would act, and how quickly?
If the answer is unclear, it’s worth reviewing your patch management process.
Cloud Context can help review patching, identify vulnerabilities and work through remediation priorities with your team. Get in touch if you’d like a hand.

Got questions, ideas, or just want to chat? We'd love to hear from you! Reach out to us anytime, and we'll get back to you with all the help and information you need.