Skip to main content

19 October 2026

Microsoft’s biggest Patch Tuesday yet, plus attacks on Cisco and BeyondTrust

Microsoft addressed more than 1,400 vulnerabilities, including one Windows flaw attackers are exploiting. Some Windows Server updates are also causing problems for Exchange. This week also covers a supplier breach settlement, device safety notices and what recovery takes beyond restoring systems.

Medical and cybersecurity shield emblem on a navy field.

Reporting window: October 12–18, 2026, America/New_York. Evidence cutoff: October 19 at 12:00 a.m. Eastern.

IT, clinical engineering and vendors will need to coordinate changes to systems used in patient care.

This week at a glance

  • Microsoft addressed more than 1,400 vulnerabilities in its October release. ZDI calls it the company’s largest monthly release to date. Microsoft says attackers are exploiting a Windows Shell flaw. Two other issues were publicly disclosed. Some Windows Server updates can also disrupt Exchange. Read about the Microsoft updates.
  • Attackers are exploiting Cisco Secure Email Gateway. The flaw affects vulnerable AsyncOS systems with AMP File Reputation assigned to a mail policy and Content Scanner Tools below 25.3.0.5525. Patching fixes the vulnerability. Suspected compromise also calls for recovery work. See Cisco’s affected systems and fixes.
  • BeyondTrust Remote Support needs a patch. BT26-05-RS applies to versions 24.3.1–26.2.3. Older self-hosted installations need an upgrade first. CISA added the flaw to its exploited list on October 16. BeyondTrust says SaaS customers were patched by October 9. Read BeyondTrust’s instructions.
  • BCHP and XTIUM agreed to a $2.7 million settlement over a 2024 intrusion. XTIUM managed the affected systems, but its contract did not include securing them. The attorneys general’s findings describe gaps in administrator access and remote-support logging. The respondents neither admitted nor denied the findings. Read what the investigation found.
  • Recovery costs include more than getting systems back online. In Proofpoint and Ponemon’s survey of 705 U.S. healthcare IT and security practitioners, disruption costs averaged $1.39 million for respondents’ costliest attack in the previous 12 months. These were self-reported estimates, and the response rate was 3.7%. Read the findings and recovery questions.

Security updates to review

Microsoft patches a Windows flaw attackers are already using

Microsoft fixed more than 1,400 vulnerabilities in its October 13 release. ZDI calls it the company’s largest monthly security release to date. Start with CVE-2026-96951, a Windows Shell security-feature bypass. Microsoft says attackers are already using it.

Microsoft also identified two publicly disclosed issues: .NET CVE-2026-108398 and CVE-2026-92707 in the third-party MessagePack-CSharp library. The MessagePack issue had been disclosed before this release. Microsoft does not identify either as exploited. Check your Windows and .NET systems and application dependencies against Microsoft’s guidance. Work with clinical engineering and your vendors before changing clinical systems.

Exchange caution: Microsoft warned on October 16 that certain October Windows Server updates can make Exchange servers unstable, including problems with Outlook on the web and mail queues. These are Windows updates, not an Exchange security update. Microsoft says not to uninstall the Windows updates. Use its linked mitigation guidance if your systems are affected.

Microsoft October security update · ZDI release analysis · NHS cyber alert · Microsoft Exchange mitigation guidance

Attackers are exploiting Cisco Secure Email Gateway — CVE-2026-76519CVSS 3.1 9.8 · CISA KEV – Known exploited · Patch the installed branch

Attackers are exploiting Cisco Secure Email Gateway

Cisco disclosed CVE-2026-76519 on October 14. The flaw can write files and run commands as root. A physical or virtual Secure Email Gateway is affected only when it runs vulnerable AsyncOS, AMP File Reputation is enabled and assigned to a mail policy, and Content Scanner Tools is below 25.3.0.5525. Cisco has patched its Secure Email Cloud infrastructure.

Patch: Upgrade to AsyncOS 15.5.5-014 or 16.5.0-780. Installations on 16.0 must migrate. On licensed, supported releases, installing Content Scanner Tools 25.3.0.5525 or later also fixes the issue without restarting the operating system. Check the installed AsyncOS and scanner versions. Cisco lists no workaround.

Compromise response: If attackers have already broken in, installing the patch won’t remove them.

If you think a virtual appliance has been breached, Cisco says to save the evidence before updating it. Then deploy a clean virtual machine running a patched software version, and set it up again without importing old configuration files. Replace its credentials and security keys where possible, and keep watching for unusual activity.

If one appliance in a cluster has been breached, Cisco strongly recommends restoring every appliance in that cluster to a secure configuration. Attackers may have stolen the SSH keys those appliances use to connect to each other.

If you think a physical appliance has been breached, contact Cisco support (TAC). Contact support as well if you can’t restore an affected appliance.

Dates: Disclosed October 14; added to CISA KEV October 14; CISA remediate-by October 17 for covered federal systems. Cisco advisory. Tracker record.

BeyondTrust Remote Support needs a patch — CVE-2026-102764CVSS 4.0 9.3 · CISA KEV – Known exploited · Apply BT26-05-RS

BeyondTrust Remote Support needs a patch

BeyondTrust says Remote Support through 26.2.3 is affected by a flaw that can bypass authentication and perform file operations on the appliance. BeyondTrust says customers running Privileged Remote Access (PRA) on their own servers should install the BT26-05 patch immediately as a precaution. PRA shares code with Remote Support (RS), but the company says its testing has not found a way to exploit this flaw in PRA. BeyondTrust update. CISA added the vulnerability to its known-exploited list on October 16.

Patch: Install BT26-05-RS on versions 24.3.1 through 26.2.3. Confirm it installed, whether you use automatic or manual patching. Older installations must upgrade before they can receive the patch. BeyondTrust says all Remote Support SaaS customers were patched by October 9.

Dates: Advisory October 15; KEV addition October 16; CISA remediate-by October 19 for covered federal systems. BeyondTrust BT26-05. Tracker record.

Breaches and healthcare research

Who was responsible for securing BCHP’s systems?

XTIUM managed the affected systems, but its contract did not include securing them.

New York and Connecticut announced the settlement on October 16 over an August 2024 intrusion that began at IT services provider XTIUM. The attorneys general say attackers reached 18 client networks. Boston Children’s Health Physicians records concerned about 825,000 New York residents and 62,871 Connecticut residents, including people whose employment information was involved.

BCHP’s separately managed active patient-record system was not breached. XTIUM notified BCHP on September 6, 2024. BCHP detected unauthorized activity on September 10 and restored its system by September 13.

The attorneys general’s findings describe gaps in remote-support logging, shared administrator access without restrictions, excessive service-account access and unresolved audit issues. The respondents neither admitted nor denied those findings. The settlement requires $2.7 million. A further $1.3 million is suspended unless they materially breach the assurance within ten years.

For your own supplier reviews, the practical question is who is responsible for securing each system, including those holding archived data. The contract and system record should agree. Administrator access and remote-support logs need an owner too.

New York Attorney General announcement · Signed assurance

Microsoft and Health-ISAC take down phishing infrastructure

Microsoft said on October 14 that it and Health-ISAC used a Southern District of Florida order to seize and redirect domains supporting YAM Store, CoGUI and Iron Man. Microsoft also disabled more than 20,000 related accounts. It said it was blocking more than 100,000 domains used for impersonation and fraud.

According to Microsoft, the wider network sent more than one billion malicious messages and targeted more than 75,000 organizations worldwide since January. Healthcare was among several targeted sectors. Those figures describe targeting and messages, not successful attacks or hospital compromises. A brand appearing in a phishing template does not mean that organization was breached. Chinese-language infrastructure does not establish government involvement.

The takedown removed some of the infrastructure behind these services, not the wider market for phishing tools. It is not a reason to relax checks on senders or requests to sign in.

Microsoft Digital Crimes Unit announcement · Microsoft technical report

Getting systems back online is only part of recovery

Proofpoint and Ponemon released their healthcare report on October 13 after surveying 705 U.S. healthcare IT and security practitioners in May. Respondents estimated an average $1.39 million in disruption costs for their single most expensive cyberattack in the preceding 12 months. That was more than any other reported cost category.

In a separate analysis covering two years, 72% of respondents whose organizations had experienced ransomware reported a negative effect on patient care. That figure applies to the ransomware-affected group, not the full sample.

These are self-reported estimates and outcomes, not independently measured costs or care outcomes. The 3.7% response rate and sample selection limit how broadly the findings apply. The survey cannot establish clinical causation.

A recovery exercise should cover more than restoring systems. Clinical teams need to work through these questions with IT:

  • How will care continue while the affected systems are unavailable?
  • Who will reconcile outstanding orders and paper records as systems return?
  • Who will decide when normal workflows can safely resume?

Proofpoint/Ponemon report · Proofpoint release

Regulation and upcoming deadlines

Comments and events

FDA wants feedback on generative AI medical devicesFeedback due October 19

FDA-2026-N-7874: generative-AI-enabled medical devices

FDA wants feedback on how to assess risk, evaluate these devices before they reach the market, and monitor them afterward. This discussion paper is neither draft nor final guidance and does not implement policy.

Action: Device manufacturers, clinicians, providers and researchers can submit evidence on those questions by October 19. FDA has not stated a closing hour or time zone.

FDA discussion paper and submission route

FDA proposes guidance for robotically assisted surgeryComments due November 24

FDA-2026-N-9505: premarket submissions for robotically assisted surgical devices

The draft covers premarket submissions for teleoperated, software-controlled surgical systems. It is nonbinding draft guidance, not guidance for implementation.

Action: Submit comments on nonclinical testing, clinical data or labeling by November 24.

FDA draft-guidance page

FDA will discuss autonomous and remotely operated medical devicesDecember 2–3, 10 a.m.–4 p.m. ET

Autonomous functions and remote teleoperation workshop

FDA’s hybrid workshop will discuss how to evaluate benefits and risks for robotic medical devices with autonomous functions or remote teleoperation. FDA had not posted the agenda or pre-workshop materials by the cutoff. In-person registration closes November 23, or earlier if the event reaches capacity; virtual registration remains available. The workshop does not create compliance requirements.

Action: Teams developing or using these systems can contribute evidence on autonomy, remote operation and human oversight. Check the FDA page for the agenda when it is posted.

FDA workshop page

FDA asks which device guidance it should work on nextComments due November 30

FDA-2012-N-1021: proposed FY2027 guidance priorities

CDRH has proposed its FY2027 priorities for developing and publishing guidance, grouped into A-list, B-list and under-construction lists. These are proposed priorities, not issued guidance.

Action: Device manufacturers, providers and researchers can comment on the priorities or suggest a guidance topic by November 30.

FDA proposed-priorities page

Updates we’re following

CISA’s incident-reporting rule is still under reviewNo final rule or effective date announced

CIRCIA final-rule status

Reginfo lists the action for the CIRCIA final rule as pending EO 12866 review, received October 1. The final rule had not been published or taken effect by the cutoff. No final-rule publication date or effective date had been announced.

Action: Prepare incident-reporting processes while waiting for the final rule and its effective date. The final reporting duties are not yet in effect.

Reginfo pending-review record

The HIPAA Security Rule proposal is still pendingJuly 2027 is a planning target

HIPAA Security Rule NPRM

Reginfo lists the proposal under Long-Term Actions, with July 2027 as the planned final-action date and no legal deadline. That is a planning target, not a compliance deadline. The current Security Rule remains in effect; the proposal has not been withdrawn or finalized in that record.

Action: Use the proposal to plan improvements while continuing to meet the current Security Rule.

Reginfo agenda entry · HHS NPRM page

The healthcare cybersecurity bill still needs House approvalPassed the Senate; not law

S. 3315 legislative status

GovInfo’s October 7 record lists October 5 as the latest action, when S. 3315 was held at the House desk. The Health Care Cybersecurity and Resiliency Act of 2026 has passed the Senate, but it has not passed the House or become law. The next House action date is unknown.

Action: Follow House action before treating the proposed terms as obligations.

October 5 Congressional Record Daily Digest

Medical devices

FDA flags four lots of Edwards Commander M

FDA’s October 15 Early Alert covers Commander M delivery systems used with SAPIEN M3. The four affected lots are 67718561, 67804014, 67887043 and 67887044. This is a potentially high-risk Early Alert, not an established Class I recall.

FDA reports three balloon bursts as of the manufacturer’s October 5 letter, with one associated death and one associated serious injury. The association does not establish causation. FDA issued its Early Alert on October 15.

Action: Stop using the four listed lots. Locate and remove them, inform the relevant clinical staff, and arrange their return with Edwards. Other lots may continue in use under the notice.

FDA Early Alert and affected lots

Medline and AVID recalls cover specific kits

FDA’s Class I communications for Medline on October 13 and AVID on October 14 tell customers to destroy the whole affected kit. Each recall covers kits containing specified BD ChloraPrep applicators. The recalls do not apply to all kits from either company.

Medline’s complete affected-product workbook lists 53 kit-and-lot combinations across 34 unique kit SKUs. AVID’s recall covers KRIV26-02, kit lot 1658437, UDI 10809160460481. Use the instructions below to check the exact affected products: Medline event 99669 and AVID event 99672.

FDA clears a tool to estimate breast cancer recurrence risk

SimBioSys announced FDA clearance for TumorSight Risk on October 15, following FDA’s September 25 substantial-equivalence decision for K260023. The Class II cloud-based medical device estimates five- and ten-year recurrence risk for adult women previously diagnosed with HR-positive, HER2-negative, N0 or N1, Stage I–IIIA breast cancer.

The device combines dynamic contrast-enhanced MRI with clinical and pathology data to support physician decisions alongside other factors. It does not diagnose cancer or select treatment autonomously. The submission describes retrospective validation in 2,129 patients at four U.S. sites, with diagnoses from 2010 through 2024. That study has not demonstrated prospective improvements in clinical outcomes. SimBioSys also discloses Mayo Clinic’s financial interest.

Before using the device, teams need to decide who checks patient eligibility and image quality, who reviews its reports, and how patient data moves to and from the cloud service.

SimBioSys announcement · FDA K260023 decision and summary

Updates we’re following

The dates below show when these Class I recalls leave our newsletter watchlist. Leaving the list does not close a recall or confirm that affected products have been addressed.

Medline recalls kits with specified ChloraPrep applicatorsClass I recall; watch ends November 10

Medline event 99669

Scope: This is a confirmed FDA Class I removal recall. The listed convenience kits contain BD item 930480 lot 4032183 or item 930299 lot 4073005. FDA’s workbook contains 53 kit-and-lot combinations across 34 unique kit SKUs. Potential Aspergillus penicillioides contamination can cause serious infection, sepsis, illness or death.

Dates: Customer letter August 11; FDA recall posting September 14; FDA Class I communication and last material update October 13. The newsletter watch ends November 10; the recall remains active.

Action: Use the complete workbook, quarantine affected kits, complete the response form and destroy the entire affected kit. This instruction applies only to the kits in the linked workbook.

FDA Class I communication · Complete FDA affected-product workbook · FDA event 99669

AVID recalls one IV Start Kit lotKRIV26-02; watch ends November 11

AVID event 99672, recall Z-3108-2026

Scope: This is a confirmed FDA Class I removal recall. The affected product is IV START KIT NON-STERILE, KRIV26-02, kit lot 1658437, UDI 10809160460481. Potential Aspergillus penicillioides contamination can cause serious infection, sepsis, illness or death.

Dates: Customer letter August 20; FDA recall posting September 14; FDA Class I communication and last material update October 14. The newsletter watch ends November 11; the recall remains active.

Action: Quarantine the listed kit, complete the response form and destroy the whole kit. This notice is separate from the AVID sodium-chloride kit recall.

FDA Class I communication and scope · FDA event 99672

Boston Scientific recalls affected Imager II cathetersStop use; watch ends October 23

Boston Scientific event 99687, recall Z-3214-2026

Last material update: FDA classified this removal recall as Class I on September 25. It remains open/classified; the newsletter watch ends October 23.

Action: Stop use and distribution, segregate affected product, verify both inner and outer UPN and lot markings, and return affected product under Boston Scientific’s instructions.

FDA Class I communication and affected-product instructions · FDA event 99687

Check Draeger VentStar Resus Neo hoses before useMP00310; watch ends October 30

Draeger event 99787

Last material update: FDA classified this removal recall as Class I on October 2. It remains open/classified. The newsletter watch ends October 30.

Action: Inspect before use and discard hoses showing cracks or detachment.

FDA Class I communication and instructions · FDA event 99787

CVE Tracker

These records stay in the newsletter for 14 days. Their removal does not mean a vulnerability has been fixed. CISA deadlines for covered federal systems are listed separately.

Open the CVE / KEV tracker17 active records

Eight of the vulnerabilities tracked below were first publicly disclosed during October 12–18. Severity and exploitation status are shown separately.

NEW

NEW · BeyondTrust Remote Support · CVE-2026-102764CISA KEV – Known exploited · Drop Nov 2

CVE-2026-102764 — BeyondTrust Remote Support

Applicability
Remote Support through 26.2.3; Privileged Remote Access is not covered.
Severity and status
CVSS 4.0 9.3. Disclosed October 15; KEV added October 16; CISA remediate-by October 19 for covered federal systems.
Dates
last material update October 16; Newsletter Drop Date November 2.

Action: Apply BT26-05-RS to 24.3.1–26.2.3; older installations must upgrade first. Verify installation. SaaS was patched by October 9.

BeyondTrust advisory · Priority treatment

NEW · Cisco Secure Email Gateway · CVE-2026-76519CISA KEV – Known exploited · Drop Nov 2

CVE-2026-76519 — Cisco Secure Email Gateway

Applicability
Physical or virtual gateway with vulnerable AsyncOS, AMP File Reputation assigned to a mail policy, and Content Scanner Tools below 25.3.0.5525.
Severity and status
CVSS 3.1 9.8. Disclosed and added to KEV October 14; CISA remediate-by October 17.
Dates
last material update October 14; Newsletter Drop Date November 2.

Action: Upgrade to AsyncOS 15.5.5-014 or 16.5.0-780, migrate 16.0, or install Content Scanner Tools 25.3.0.5525+ where supported. Investigate suspected compromise separately.

Cisco advisory · Priority treatment

NEW · Palo Alto Networks PAN-OS · CVE-2026-0322CISA KEV – Known exploited · Drop Nov 2

CVE-2026-0322 — PAN-OS management interface

Applicability
Affected PA-Series, VM-Series and Panorama management interfaces; Cloud NGFW and Prisma Access are unaffected.
Severity and status
CVSS 4.0 8.6. Disclosed October 14, updated October 15; KEV added October 14; CISA remediate-by October 17.
Dates
last material update October 15; Newsletter Drop Date November 2.

Action: Apply the fixed build for the exact PAN-OS branch and migrate unsupported releases. Restrict management access while patching; signatures are conditional coverage, not the fix.

Palo Alto Networks advisory · Priority treatment

NEW · Ivanti Connect Secure · CVE-2026-104935CISA KEV – Known exploited · Drop Nov 2

CVE-2026-104935 — Ivanti Connect Secure

Applicability
Ivanti's CVE record contains conflicting version-scope fields; confirm your release against its Hub advisory.
Severity and status
CVSS 3.1 8.6. Disclosed and added to KEV October 13; CISA remediate-by October 16.
Dates
last material update October 13; Newsletter Drop Date November 2.

Action: Use Ivanti's Hub advisory to confirm the upgrade path, prerequisites and recovery procedure for your release.

Ivanti Hub advisory · Priority treatment

NEW · Windows Shell / Outlook.com · CVE-2026-96951CISA KEV – Known exploited · Drop Nov 2

CVE-2026-96951 — Microsoft Windows Shell and Outlook.com

Applicability
Multiple supported Windows client and server branches, including Server Core distinctions, plus Outlook.com. The CVE record lists affected-build limits rather than installation instructions.
Severity and status
CVSS 3.1 8.8. Disclosed and added to KEV October 13; CISA remediate-by October 16.
Dates
last material update October 16; Newsletter Drop Date November 2.

Action: Use Microsoft Security Update Guide to identify the update for your Windows edition, architecture and Server Core configuration.

Microsoft Security Update Guide

NEW · Microsoft Outlook for Windows · CVE-2026-70242Not in CISA KEV at cutoff · Drop Nov 2

CVE-2026-70242 — Microsoft Outlook for Windows

Applicability
Microsoft 365 Apps for Enterprise and Office LTSC 2021 or 2024 on 32-bit or x64 Windows. The cited record does not list Mac versions for this flaw.
Severity and status
CVSS 3.1 9.8. Disclosed October 13. No exploitation was confirmed in the cited records; no CISA remediate-by date was listed at cutoff.
Dates
last material update October 13; Newsletter Drop Date November 2.

Action: Install the build matching the installed product and channel: LTSC 2021 14334.20974; LTSC 2024 17932.21056; Current Channel 2609 20430.20182; or Microsoft’s applicable Monthly or Semi-Annual Enterprise build. Verify the resulting build.

Microsoft Office security update table

NEW · Outlook for Windows and Mac · CVE-2026-70291Not in CISA KEV at cutoff · Drop Nov 2

CVE-2026-70291 — Microsoft Outlook for Windows and Mac

Applicability
Microsoft 365 Apps for Enterprise and Office LTSC 2021 or 2024 on Windows, plus Office 365 for Mac and Office LTSC for Mac 2021 or 2024.
Severity and status
CVSS 3.1 9.8. Disclosed October 13; Mac build published October 14. No exploitation was confirmed in the cited records; no CISA remediate-by date was listed.
Dates
last material update October 14; Newsletter Drop Date November 2.

Action: On Windows, install the matching build in Microsoft’s October 13 table. On Mac, install 16.114 build 26101123 or later. Verify the resulting build.

Windows channel builds · Mac release notes

NEW · GlobalProtect for macOS · CVE-2026-0315Not in CISA KEV at cutoff · Drop Nov 2

CVE-2026-0315 — Palo Alto Networks GlobalProtect for macOS

Applicability
macOS 6.3.0–6.3.3-h15 or 6.2.0–6.2.8-h14. Windows, Linux, iOS, Android and ChromeOS are unaffected.
Severity and status
CVSS 4.0 base 8.5; vendor threat-adjusted score 5.9. Disclosed October 14. No malicious exploitation was known to the vendor; no CISA remediate-by date was listed.
Dates
last material update October 14; Newsletter Drop Date November 2.

Action: Update to 6.3.3-h16 (6.3.3-1199), 6.2.8-h15 (6.2.8-1084), or later. No workaround is listed.

Palo Alto Networks advisory

Current-window additions and material updates

Fortinet products · CVE-2025-61624CISA KEV – Known exploited · Drop Nov 2

CVE-2025-61624 — Fortinet multiple products

Applicability
An authenticated administrator with at least read-write CLI permissions can modify or delete files in listed products.
Severity and status
CVSS 3.1 5.4. First disclosed April 14; KEV added October 16; CISA remediate-by October 19.
Dates
last material update October 16; Newsletter Drop Date November 2.

Action: April’s vendor mapping lists FortiOS 7.6.5 or 7.4.10, FortiProxy 7.6.5 or 7.4.12, FortiPAM 1.8.0 or 1.7.1, FortiSwitch 7.6.5 or 7.4.9, and FortiSwitchManager 7.2.8 or 7.0.7, or later appropriate releases. Confirm branch support and release availability in the current advisory before upgrading.

Fortinet advisory

AhsayCBS · CVE-2026-105133CISA KEV – Known exploited · Drop Nov 2

CVE-2026-105133 — AhsayCBS

Applicability
Affected v7, v8, v9 and v10 installations; the flaw can chain with CVE-2026-105134.
Status
Original disclosure date not established. Replacement-fix correction October 12; KEV added October 14; CISA remediate-by October 17.
Dates
last material update October 14; Newsletter Drop Date November 2.

Action: Install 10.3.4.45 for v10 or 9.15.2.70 for v7–v9, replacing the incomplete fix, then reboot.

Ahsay correction · Priority treatment

AhsayCBS · CVE-2026-105134CISA KEV – Known exploited · Drop Nov 2

CVE-2026-105134 — AhsayCBS

Applicability
Affected v7, v8, v9 and v10 installations; the flaw can chain with CVE-2026-105133.
Status
Original disclosure date not established. Replacement-fix correction October 12; KEV added October 14; CISA remediate-by October 17.
Dates
last material update October 14; Newsletter Drop Date November 2.

Action: Install 10.3.4.45 for v10 or 9.15.2.70 for v7–v9, replacing the incomplete fix, then reboot.

Ahsay correction · Priority treatment

Atlassian Data Center products · CVE-2026-21589CISA KEV – Known exploited · Drop Oct 26

CVE-2026-21589 — Atlassian products

Applicability
Self-managed Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo, Crowd, Crucible and Fisheye Data Center products. Cloud was patched.
Severity and status
CVSS 4.0 9.3. First disclosed October 5; KEV added October 15; CISA remediate-by October 18.
Dates
last material update October 15; Newsletter Drop Date October 26.

Action: Apply Atlassian’s product-specific fixed release. Access restriction is temporary; investigate protected-file access and rotate exposed secrets separately.

Atlassian advisory · Priority treatment

Continuing watch

ISC BIND · CVE-2015-5477CISA KEV – Known exploited · Drop Oct 26

CVE-2015-5477 — ISC BIND TKEY denial of service

Historical disclosure; KEV added October 8; CISA remediate-by October 11. last material update October 8; Newsletter Drop Date October 26.

Action: Use a supported vendor package. Debian bookworm is fixed at 1:9.18.49-1~deb12u1 and trixie at 1:9.20.26-1~deb13u1; Ubuntu’s listed Trusty, Precise and Vivid fixes are historical, not current deployment targets. Restart or reload as directed and verify the installed package and running process. ISC supplied no workaround.

ISC advisory · Debian status · Ubuntu status

Apache Struts · CVE-2016-3081CISA KEV – Known exploited · Drop Oct 26

CVE-2016-3081 — Apache Struts

Applies to Struts 2.3.20–2.3.28 except 2.3.20.3 and 2.3.24.3 when Dynamic Method Invocation is enabled. Historical disclosure; KEV added October 8; CISA remediate-by October 11. last material update October 8; Newsletter Drop Date October 26.

Action: Move to a currently supported Struts release. Disabling Dynamic Method Invocation is temporary risk reduction. Hunt method-prefixed malicious requests and investigate post-exploitation separately.

Apache S2-032 advisory

Strapi · CVE-2023-22894CISA KEV – Known exploited · Drop Oct 26

CVE-2023-22894 — Strapi

Applies to Strapi 3.2.1 and later before 4.8.0; v3 is end of life. Historical disclosure; KEV added October 8; CISA remediate-by October 11. last material update October 8; Newsletter Drop Date October 26.

Action: Move to a currently supported release, using Strapi 5 where applicable; 4.8.0 is only the historical fixed boundary. Review suspicious query parameters as triage leads, not proof.

Strapi disclosure · GitHub advisory

ONLYOFFICE Document Server · CVE-2021-3199CISA KEV – Known exploited · Drop Oct 26

CVE-2021-3199 — ONLYOFFICE Document Server

Historical affected boundary is before 5.6.3 when JWT is used. KEV added October 8; CISA remediate-by October 11. last material update October 8; Newsletter Drop Date October 26.

Action: Install a currently supported ONLYOFFICE Docs release from the official package or container channel, restart or redeploy, and verify the running version. Version 5.6.3 is only the historical fix boundary.

ONLYOFFICE changelog

ProFTPD mod_copy · CVE-2015-3306CISA KEV – Known exploited · Drop Oct 26

CVE-2015-3306 — ProFTPD mod_copy

Remote unauthenticated use of SITE CPFR and SITE CPTO is possible when mod_copy is enabled. Historical disclosure; KEV added October 8; CISA remediate-by October 11. last material update October 8; Newsletter Drop Date October 26.

Action: Debian bookworm is fixed at 1.3.8+dfsg-4+deb12u5 and trixie at 1.3.8.c+dfsg-4+deb13u3. Ubuntu’s Trusty, Precise and Vivid fixes are historical; Xenial and Yakkety were marked not affected. Confirm the package, loaded module and running daemon. Disable mod_copy temporarily on a self-built legacy service and migrate to a supported release.

Debian status · Ubuntu status

Records leave routine display after 14 days of CCD tracking. That is not proof of remediation; federal remediation deadlines remain separate.

Updates for four more products
Ahsay says its earlier patches did not fully fix two flaws — CVE-2026-105133 / CVE-2026-105134CVSS not verified · CISA KEV – Known exploited · Validate upgrade and investigate

Ahsay says its earlier patches did not fully fix two flaws

Ahsay said on October 12 that patches 9.15.2.59 and 10.3.4.0 did not fully fix these flaws. CVE-2026-105133 can bypass authentication. CVE-2026-105134 allows command injection and execution. An attacker can chain the two. The original disclosure date is unknown; October 12 was the correction date.

Patch: Replace the earlier fixes with 10.3.4.45 on affected v10 installations or 9.15.2.70 on affected v7, v8 or v9 installations. Then reboot the server as Ahsay directs. You need an existing partner login to download the hotfixes.

Dates: Replacement-fix correction October 12; both CVEs added to KEV October 14; CISA remediate-by October 17 for covered federal systems. Ahsay correction. Tracker: CVE-2026-105133 and CVE-2026-105134.

Palo Alto Networks reports limited attacks on PAN-OS — CVE-2026-0322CVSS 4.0 8.6 · CISA KEV – Known exploited · Patch affected PAN-OS branches

Palo Alto Networks reports limited attacks on PAN-OS

Palo Alto Networks reports very limited attacks exploiting this flaw. An authenticated attacker can run code as root through affected PA-Series, VM-Series and Panorama management interfaces. Cloud NGFW and Prisma Access are not affected.

Patch: Choose the fixed build for your exact maintenance branch. Fixed builds include 12.2.4; 12.1.4-h12, 12.1.7-h8 or 12.1.10-h2; 11.2.4-h22, 11.2.7-h21, 11.2.10-h15, 11.2.13-h3 or 11.2.16; 11.1.4-h37, 11.1.6-h39, 11.1.7-h11, 11.1.10-h35, 11.1.13-h15 or 11.1.16-h3; and 10.2.7-h38, 10.2.10-h41, 10.2.13-h26, 10.2.16-h11 or 10.2.18-h12. If your version is unsupported, migrate to a supported release.

Mitigation: While you patch, limit management access to trusted internal administration paths. Threat Prevention signatures cover only some conditions. They do not fix the vulnerability.

Dates: Disclosed October 14, updated October 15; KEV addition October 14; CISA remediate-by October 17 for covered federal systems. Palo Alto Networks advisory. Tracker record.

Ivanti users need to check the fix for their installed version — CVE-2026-104935CVSS 3.1 8.6 · CISA KEV – Known exploited · Validate Ivanti guidance

Ivanti users need to check the fix for their installed version

This command-execution flaw is being exploited, but Ivanti’s CVE record contains conflicting version information. It lists 25.1.3.0, 25.1.3.1, 22.8R2.5 and 22.7R2.14 as unaffected. Its description also excludes 22.7R2.14 and earlier. That record alone does not establish a complete affected-version range.

Action: Check Ivanti’s Hub advisory for the upgrade path, prerequisites and recovery instructions for your installed release. The cited CVE record does not provide a complete upgrade or workaround procedure.

Dates: Vendor-authored record October 13; KEV addition October 13; CISA remediate-by October 16 for covered federal systems. Ivanti Hub advisory. Vendor-authored CVE record. Tracker record.

CISA adds an Atlassian file-access flaw to its exploited list — CVE-2026-21589CVSS 4.0 9.3 · CISA KEV – Known exploited · Patch affected Data Center products

CISA adds an Atlassian file-access flaw to its exploited list

Atlassian disclosed this unauthenticated file-access flaw on October 5, before this edition’s window. CISA added it to its known-exploited list on October 15. It affects self-managed Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo, Crowd, Crucible and Fisheye Data Center products. Atlassian has patched its Cloud service; Cloud customers do not need to act.

Patch: Use the fixed release for your product in Atlassian’s table: Bitbucket 9.4.26, 10.2.8 or 10.5.1; Confluence 9.2.26 or 10.2.19; Jira Service Management 5.12.40, 10.3.26 or 11.3.12; Jira Software 9.12.40, 10.3.26 or 11.3.12; Bamboo 10.2.24 or 12.1.12; Crowd 6.3.7, 7.0.3, 7.1.7 or 7.2.4; and Crucible or Fisheye 4.9.15. A later supported release is also an option.

Mitigation and investigation: Restricting external access or using Atlassian’s exact request-blocking patterns is temporary. URL-decode access logs and look for requests for protected configuration files. Investigate that access and rotate exposed secrets separately from checking that the patch installed.

Dates: Disclosure October 5; KEV addition October 15; CISA remediate-by October 18 for covered federal systems. Atlassian advisory. Tracker record.

Sources

Sources and dates

Vulnerabilities and exploitation status

Healthcare incidents and research

Medical-device clearance, regulatory and legislative records

Medical devices

Clinical Cyber Dispatch

Independent healthcare cybersecurity analysis for security and technology leaders.