---
title: "Forty-Eight Hours: ASD's Critical Alert Says Your Patch Window Has Shrunk"
description: "ASD's ACSC issued a critical alert on 17 November 2026: some flaws are exploited within 48 hours of a fix. How to patch, protect and prevent at that pace."
image: https://www.alchemysec.com.au/hubfs/blog/asd-critical-alert-48-hour-patch-window/featured-asd-48-hour-window.jpg
---

[Go Back Up](https://www.alchemysec.com.au/blog/asd-critical-alert-48-hour-patch-window#top)

[Skip to Content](https://www.alchemysec.com.au/blog/asd-critical-alert-48-hour-patch-window#body)

**University of Sydney Code Library Breach:** Disclosed 18 Dec, 2025

Personal details of about 27,500 current and former staff exposed.

18 Dec 2025 - Syd Uni breached

[Read more](https://www.sydney.edu.au/news-opinion/news/2025/12/18/notification-of-cyber-and-data-breach.html)

[![Alchemy\_Security\_Consulting\_Logo\_B2\_Cropped\_White\_400](https://www.alchemysec.com.au/hs-fs/hubfs/Alchemy_Security_Consulting_Logo_B2_Cropped_White_400.png?width=200&name=Alchemy_Security_Consulting_Logo_B2_Cropped_White_400.png)](https://www.alchemysec.com.au/)

- Offensive Security
- Defensive Security
- Managed Services
- Company
- Resources

[Have you been breached?](https://www.alchemysec.com.au/breached) [Book a consult](https://www.alchemysec.com.au/contact)

[Offensive Security](https://www.alchemysec.com.au/services/offensive) [Penetration Testing](https://www.alchemysec.com.au/services/offensive/pentest) [Red Teaming](https://www.alchemysec.com.au/services/offensive/red-teaming) [Adversary Simulation](https://www.alchemysec.com.au/services/offensive/adversary-simulation) [Purple Teaming](https://www.alchemysec.com.au/services/offensive/purple-teaming)

[Defensive Security](https://www.alchemysec.com.au/services/defensive) [Incident Response](https://www.alchemysec.com.au/breached) [SIEM, Logging & Detection Engineering](https://www.alchemysec.com.au/services/defensive/siem-logging)

[Managed Services](https://www.alchemysec.com.au/services/managed) [Managed Detection & Response](https://www.alchemysec.com.au/services/managed/mdr) [Managed SOC](https://www.alchemysec.com.au/services/managed/soc) [Continuous Threat Emulation](https://www.alchemysec.com.au/services/managed/continuous-threat-emulation)

[About Us](https://www.alchemysec.com.au/about) [Contact Us](https://www.alchemysec.com.au/contact)

[Blog](https://www.alchemysec.com.au/blog)

- Offensive Security
  
  [Offensive Security](https://www.alchemysec.com.au/services/offensive) [Penetration Testing](https://www.alchemysec.com.au/services/offensive/pentest) [Red Teaming](https://www.alchemysec.com.au/services/offensive/red-teaming) [Adversary Simulation](https://www.alchemysec.com.au/services/offensive/adversary-simulation) [Purple Teaming](https://www.alchemysec.com.au/services/offensive/purple-teaming)
- Defensive Security
  
  [Defensive Security](https://www.alchemysec.com.au/services/defensive) [Incident Response](https://www.alchemysec.com.au/breached) [SIEM, Logging & Detection Engineering](https://www.alchemysec.com.au/services/defensive/siem-logging)
- Managed Services
  
  [Managed Services](https://www.alchemysec.com.au/services/managed) [Managed Detection & Response](https://www.alchemysec.com.au/services/managed/mdr) [Managed SOC](https://www.alchemysec.com.au/services/managed/soc) [Continuous Threat Emulation](https://www.alchemysec.com.au/services/managed/continuous-threat-emulation)
- Company
  
  [About Us](https://www.alchemysec.com.au/about) [Contact Us](https://www.alchemysec.com.au/contact)
- Resources
  
  [Blog](https://www.alchemysec.com.au/blog)

[Have you been breached?](https://www.alchemysec.com.au/breached) [Book a consult](https://www.alchemysec.com.au/contact)

# Forty-Eight Hours: ASD's Critical Alert Says Your Patch Window Has Shrunk

[Blog](https://www.alchemysec.com.au/blog/tag/blog) [Defence](https://www.alchemysec.com.au/blog/tag/defence) [Emerging Threats](https://www.alchemysec.com.au/blog/tag/emerging-threats) 18 November 2026 6 min read

![Japanese woodblock print style illustration of an elderly gatekeeper in an indigo robe pushing a heavy wooden castle gate shut as a towering great wave rolls in behind it, with a large hourglass on the stone wall beside him running down](https://www.alchemysec.com.au/hs-fs/hubfs/blog/asd-critical-alert-48-hour-patch-window/featured-asd-48-hour-window.jpg?width=1000&name=featured-asd-48-hour-window.jpg)

<https://twitter.com/intent/tweet/?text=Forty-Eight+Hours%3A+ASD%27s+Critical+Alert+Says+Your+Patch+Window+Has+Shrunk&url=https%3A%2F%2Fwww.alchemysec.com.au%2Fblog%2Fasd-critical-alert-48-hour-patch-window> <https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.alchemysec.com.au%2Fblog%2Fasd-critical-alert-48-hour-patch-window> <https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.alchemysec.com.au%2Fblog%2Fasd-critical-alert-48-hour-patch-window> [mailto:?subject=Forty-Eight%20Hours%3A%20ASD%27s%20Critical%20Alert%20Says%20Your%20Patch%20Window%20Has%20Shrunk&body=https%3A%2F%2Fwww.alchemysec.com.au%2Fblog%2Fasd-critical-alert-48-hour-patch-window](mailto:?subject=Forty-Eight%20Hours%3A%20ASD%27s%20Critical%20Alert%20Says%20Your%20Patch%20Window%20Has%20Shrunk&body=https%3A%2F%2Fwww.alchemysec.com.au%2Fblog%2Fasd-critical-alert-48-hour-patch-window)

On 17 November 2026 the Australian Signals Directorate's Australian Cyber Security Centre (ASD's ACSC) published a critical alert that doesn't name a single product. There's no Common Vulnerabilities and Exposures (CVE) number to look up and no vendor to chase. Its title is the whole message: [Vulnerabilities are moving quickly, so patch, protect, prevent](https://www.cyber.gov.au/alert/vulnerabilities-are-moving-quickly-so-patch-protect-prevent).

That's unusual. ASD's ACSC keeps its critical rating for problems that are affecting Australia now or will imminently, with active exploitation and exploit code that's easy to use. This time the problem it describes is the pace of the whole patch cycle. In this post we'll look at what the alert says, what the last few weeks looked like from the attacker's side, and how to set up your patching so two days is actually achievable.

## Key takeaways

- ASD's ACSC says some vulnerabilities were exploited within 48 hours of patches or mitigation advice becoming available, and publicly reported vulnerabilities rose 30 per cent last financial year.
- The advice comes in three parts: patch faster, shrink what's exposed to the internet, and watch for signs of exploitation.
- The 48-hour target isn't new. The Essential Eight already expects critical or actively exploited flaws in internet-facing services to be patched within 48 hours, from Maturity Level One.

## What the alert actually says

The alert draws on ASD's Annual Cyber Threat Report 2025-26. It notes that publicly reported software vulnerabilities rose 30 per cent last financial year, that some were exploited within 48 hours of a fix or advice appearing, and that automated and artificial intelligence (AI) enabled tools are helping attackers find and exploit weaknesses across more systems, more quickly. The conclusion is blunt: expect more frequent updates and less time to apply them.

We looked at the detection side of that same report [earlier this month](https://www.alchemysec.com.au/blog/who-found-it-first-asd-2025-26-threat-report). This alert is the patching side.

## A few weeks in the life of the window

If 48 hours sounds alarmist, three recent cases show how it plays out:

- **Puppet:** On 3 November Perforce [fixed CVE-2026-115731](https://www.puppet.com/products/puppet-enterprise/whats-new) in Puppet Enterprise, a flaw that lets anyone holding an agent certificate run code on the Puppet Server by sending it a crafted report. On 17 November the US Cybersecurity and Infrastructure Security Agency (CISA) [added it](https://www.cisa.gov/news-events/alerts/2026/11/17/cisa-adds-one-known-exploited-vulnerability-catalog) to its Known Exploited Vulnerabilities (KEV) catalogue. A Puppet Server tells every managed machine how to configure itself, so whoever controls it controls the fleet.
- **N-able N-central:** When a public exploit chain for N-central appeared on 12 November, researchers found compromised servers [within hours](https://www.bleepingcomputer.com/news/security/new-n-able-4everable2shell-zero-day-exploited-hours-after-poc-released/), most of them already on the latest hotfix.
- **ScreenConnect:** ConnectWise fixed CVE-2026-84869 on 8 September. On 12 November [Huntress saw](https://www.huntress.com/blog/cve-2026-84869-screenconnect-technician-exploitation) a technician's workstation at a managed service provider (MSP) compromised through a ScreenConnect client that was still vulnerable, and counted about 688,000 attempts against 42 MSP servers since 20 October.

All three are tools used by the people who manage your systems. That's why the alert asks you to confirm that suppliers can promptly patch the systems they run on your behalf, and why the ScreenConnect case matters: the fix had existed for two months, it just never reached the technician's laptop.

## Making two days realistic

Nobody patches everything in 48 hours, and the Essential Eight doesn't ask you to. Its [maturity model](https://www.cyber.gov.au/publication/essential-eight-maturity-model) sets 48 hours for online services when the vendor rates a flaw critical or a working exploit exists, and two weeks otherwise. The trick is knowing in advance which systems sit in the fast lane. Before the next critical alert lands:

- **Inventory:** keep a current list of everything reachable from the internet, including edge devices, remote access tools and management consoles, with an owner for each.
- **Triage:** check CISA's KEV catalogue and ASD's ACSC alerts daily, and treat "exploited" as the trigger for the 48-hour lane whatever the severity score says.
- **Pre-approval:** agree emergency change rules now, so an urgent patch doesn't wait for next week's change board.
- **Suppliers:** ask each MSP and software as a service (SaaS) provider how fast they patch critical flaws, and get the answer written into the contract.
- **Agents and clients:** include technician tools, agents and desktop clients in patch reporting, not only servers.

When a patch can't go on straight away, the alert says to assess the risk, restrict exposure and add temporary controls. In practice that means:

- Take the service off the internet, or put it behind a virtual private network (VPN) or an allow list, until it's fixed.
- Apply the vendor's interim mitigation. For Puppet, Red Hat's guidance is to stop autosigning certificate requests without strong verification.
- Strengthen multi-factor authentication (MFA) on every administrative path into the system.
- Retire what can't be fixed. Unsupported systems are, in the alert's words, easy targets.

## Patch, then check

The window cuts both ways. If a flaw was exploited two days after release and you patched on day five, the patch shuts the door but tells you nothing about whether someone walked through it first. CISA's new Binding Operational Directive (BOD) 26-04 now sets expectations for when US federal agencies must check for compromise before the patch went on. It's good practice for everyone. After patching an exploited flaw:

- Review logs on the patched system back to the disclosure date.
- Look for new accounts, scheduled tasks, services or remote access tools nobody can explain.
- For management platforms such as Puppet or remote monitoring and management (RMM) tools, check what they pushed to managed machines during that period.

On our incident response engagements we regularly find the patch went on within the organisation's own timeframe, just a few days after somebody else got there.

## How Alchemy Security can help

Alchemy Security's penetration testing finds the internet-facing services you didn't know you had before an attacker's scanner does, and our Managed Detection and Response (MDR) service watches for exploitation in the days between disclosure and patch. If you'd like help building a 48-hour lane, or checking whether a recent flaw was used against you, [get in touch](https://www.alchemysec.com.au/contact).

## Conclusion

There's no product to patch in this alert, which makes it easy to read and file. Don't. The next critical flaw will arrive with a CVE number and a very short clock, and the organisations that cope will be the ones that decided in advance what gets patched first and who does it.

*Last updated: 18 November 2026*

## References

- ASD's ACSC, Vulnerabilities are moving quickly, so patch, protect, prevent: [https://www.cyber.gov.au/alert/vulnerabilities-are-moving-quickly-so-patch-protect-prevent](https://www.cyber.gov.au/alert/vulnerabilities-are-moving-quickly-so-patch-protect-prevent)
- ASD's ACSC, Essential Eight Maturity Model: [https://www.cyber.gov.au/publication/essential-eight-maturity-model](https://www.cyber.gov.au/publication/essential-eight-maturity-model)
- CISA, CISA Adds One Known Exploited Vulnerability to Catalog (17 November 2026): [https://www.cisa.gov/news-events/alerts/2026/11/17/cisa-adds-one-known-exploited-vulnerability-catalog](https://www.cisa.gov/news-events/alerts/2026/11/17/cisa-adds-one-known-exploited-vulnerability-catalog)
- CISA, Known Exploited Vulnerabilities Catalog: [https://www.cisa.gov/known-exploited-vulnerabilities-catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)
- Puppet, Updates and Releases for Puppet Enterprise (CVE-2026-115731 security update): [https://www.puppet.com/products/puppet-enterprise/whats-new](https://www.puppet.com/products/puppet-enterprise/whats-new)
- GitHub Advisory Database, CVE-2026-115731: [https://github.com/advisories/GHSA-4PXX-8FRQ-9R4J](https://github.com/advisories/GHSA-4PXX-8FRQ-9R4J)
- Red Hat, CVE-2026-115731: [https://access.redhat.com/security/cve/cve-2026-115731](https://access.redhat.com/security/cve/cve-2026-115731)
- BleepingComputer, New N-able "4EverAble2Shell" zero-day exploited hours after PoC released: [https://www.bleepingcomputer.com/news/security/new-n-able-4everable2shell-zero-day-exploited-hours-after-poc-released/](https://www.bleepingcomputer.com/news/security/new-n-able-4everable2shell-zero-day-exploited-hours-after-poc-released/)
- Huntress, CVE-2026-84869 in ScreenConnect Exploited to Run Malicious Files on MSP Technician Accounts: [https://www.huntress.com/blog/cve-2026-84869-screenconnect-technician-exploitation](https://www.huntress.com/blog/cve-2026-84869-screenconnect-technician-exploitation)

## Ready to Transform your Business with Little Effort Using Brightlane?

[Register Now](https://www.example.com)

You May Like These

## Related Articles

![](https://www.alchemysec.com.au/hs-fs/hubfs/blog/who-found-it-first-asd-2025-26-threat-report/featured-who-found-it-first.jpg?width=700&name=featured-who-found-it-first.jpg)

### [Who Found It First? Detection Lessons From ASD's 2025-26 Threat Report](https://www.alchemysec.com.au/blog/who-found-it-first-asd-2025-26-threat-report)

![](https://www.alchemysec.com.au/hs-fs/hubfs/blog/patched-isnt-clean/featured-patched-isnt-clean.jpeg?width=700&name=featured-patched-isnt-clean.jpeg)

### [Patched Isn't Clean: PHP2Shell and the NetScaler SAML Saga](https://www.alchemysec.com.au/blog/patched-isnt-clean-php2shell-netscaler)

![](https://www.alchemysec.com.au/hs-fs/hubfs/Imported_Blog_Media/envelope-01-1024x572.jpg?width=700&name=envelope-01-1024x572.jpg)

### [Please Sign Here - Why NTLM Relaying Is Still a Risk in 2021](https://www.alchemysec.com.au/blog/please-sign-here-why-ntlm-relaying-is-still-a-risk-in-2021)

---

![Alchemy Security Consulting](https://www.alchemysec.com.au/hubfs/Images/Logos/Alchemy/Alchemy_Security_Consulting_Logo_B2_Cropped_White_350.png)

 Offensive, defensive and managed security expertise to help you understand your exposure, strengthen your defences and validate improvement.

#### Get In Touch

##### Location

 30 Pirie St, Adelaide, South Australia 5000

##### Contact

###### Phone :

[1300 792 870](tel:+611300792870)

###### Email :

[sales@alchemysec.com.au](mailto:sales@alchemysec.com.au)

#### Services

- [Penetration Testing](https://www.alchemysec.com.au/services/offensive/pentest)
- [Red Teaming](https://www.alchemysec.com.au/services/offensive/red-teaming)
- [Adversary Simulation](https://www.alchemysec.com.au/services/offensive/adversary-simulation)
- [Purple Teaming](https://www.alchemysec.com.au/services/offensive/purple-teaming)
- [Incident Response](https://www.alchemysec.com.au/breached)
- [SIEM, Logging & Detection Engineering](https://www.alchemysec.com.au/services/defensive/siem-logging)
- [Managed Detection & Response](https://www.alchemysec.com.au/services/managed/mdr)
- [Managed SOC](https://www.alchemysec.com.au/services/managed/soc)
- [Continuous Threat Emulation](https://www.alchemysec.com.au/services/managed/continuous-threat-emulation)

#### Company

- [About Us](https://www.alchemysec.com.au/about)
- [Blog](https://www.alchemysec.com.au/blog)
- [Contact](https://www.alchemysec.com.au/contact)
- [Book a Consult](https://www.alchemysec.com.au/contact)
- [Privacy Policy](https://www.alchemysec.com.au/privacy-policy)

© Alchemy Security. All rights reserved | [Privacy Policy](https://www.alchemysec.com.au/privacy-policy)

Cookie settings

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person"
  },
  "dateModified" : "2026-11-18T01:18:23.252Z",
  "datePublished" : "2026-11-18T01:21:19.000Z",
  "headline" : "Forty-Eight Hours: ASD's Critical Alert Says Your Patch Window Has Shrunk",
  "image" : [ "https://www.alchemysec.com.au/hubfs/blog/asd-critical-alert-48-hour-patch-window/featured-asd-48-hour-window.jpg" ],
  "mainEntityOfPage" : {
    "@id" : "https://www.alchemysec.com.au/blog/asd-critical-alert-48-hour-patch-window",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.alchemysec.com.au/hubfs/Alchemy_Security_Consulting_Logo_B2_Cropped_White_300.png"
    }
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://alchemysec.com.au/#organization",
  "@type" : "Organization",
  "address" : {
    "@type" : "PostalAddress",
    "addressCountry" : "AU",
    "addressLocality" : "Adelaide",
    "addressRegion" : "SA",
    "postalCode" : "5000",
    "streetAddress" : "30 Pirie St"
  },
  "description" : "Cybersecurity consultancy providing offensive security, defensive security and managed security services.",
  "email" : "sales@alchemysec.com.au",
  "name" : "Alchemy Security Consulting",
  "telephone" : "+611300792870",
  "url" : "https://alchemysec.com.au/"
}
```