Opens in a new tab

Daily Security Briefing: Saturday, October 31, 2026

  • Home
  • Blog
  • Daily Security Briefing: Saturday, October 31, 2026
Daily security briefing featuring cracked server exposing root access vulnerabilities
Updated October 31, 2026 at 7:54 PM ET

Review the reported issues below to confirm where they apply and prioritize the next checks. The alert set covers exploited Ivanti flaws, a Binance theft, DDoS activity, a Linux kernel vulnerability and a ChatGPT link flaw.

Issue Confirmed status Affected environment Priority Reference
Ivanti Connect Secure Exploited in the wild Remote-access appliance users Immediate CISA KEV and NVD
Binance theft Company reports user assets are covered Binance account users High Gizmodo
Cloudflare DDoS activity Vendor reports mitigation totals Website and internet-facing services High Cloudflare
Linux kernel flaw Remote code execution demonstrated Linux servers with an MPTCP listener High BleepingComputer
Shared ChatGPT link Vendor reproduced and fixed; no exploitation reported Signed-in ChatGPT web users Medium The Hacker News

What happened

The report said the flaws have been exploited in the wild, with post-exploitation activity including credential theft, limited Active Directory metadata collection, reconnaissance and searches for administrator passwords and BitLocker recovery keys.

In separate reports, Binance covered a $6.3 billion theft attributed to Binance, while Cloudflare published its Q3 2026 DDoS threat report. A report covered a Linux kernel vulnerability, and a report covered a ChatGPT shared-link flaw that OpenAI reproduced and fixed.

What to do now

Ivanti Connect Secure: patch and review access records

The report identifies Ivanti Connect Secure 25.1.1.2 and prior and 22.8R2.5 and prior as affected. It identifies the flaws as CVE-2026-111357 and CVE-2026-118527, with patches available in versions 25.1.1.3 and 22.8R2.6.

  1. Confirm whether your organization runs Ivanti Connect Secure and identify the deployed version.
  2. Apply the vendor’s available patch to the affected appliance.
  3. Review the appliance for signs of compromise after the update.
  4. Rotate credentials that may have been exposed and address any discovered access to Active Directory, administrator accounts or BitLocker recovery keys.

What changed since this was first reported: Check the current source for the affected versions, patch availability and post-exploitation behavior.

Binance: wait for the withdrawal service to resume

Binance said the $6.3 billion theft left user assets covered and described all user assets as safe. That is the company’s assertion; the source did not provide independent verification of the coverage or the recovery of every stolen wallet.

Withdrawals were halted, and Binance said it aimed to resume them within approximately 34 hours, subject to security checks. It also said it froze about $3 billion of stolen cryptocurrency with partners, without indicating whether the remaining $3.3 billion was secured.

  1. Check Binance’s official service and withdrawal status before attempting a withdrawal.
  2. Wait until the company confirms that security checks are complete and withdrawals have resumed.
  3. Follow any further instructions issued by Binance for affected accounts.

What changed since this was first reported: Check Binance’s official service status for the current withdrawal status.

Cloudflare: review DDoS monitoring and coverage

Cloudflare reported that it mitigated 18.2 million network-layer DDoS attacks and 14.4 trillion HTTP DDoS requests in Q3 2026. The company reported about 8,226 network-layer attacks per hour, while attacks exceeding 1 Tbps declined by 69% from the prior quarter. DNS amplification attacks increased by 215%, and the report identified new variants including Dysphoria and Evooo1Bot.

The underlying Cloudflare report gives more context. Network-layer mitigation traffic totaled 272.6 petabytes, while HTTP-layer traffic totaled 95.1 petabytes. Ninety-six percent of network-layer attacks ended in under 10 minutes, and 98% remained below 1 Gbps. The report also recorded four days in August when Mirai-classified mitigation exceeded three petabytes each, with the longest sustained Mirai attack lasting 49.7 hours.

  1. Confirm which internet-facing services need DDoS monitoring and mitigation.
  2. Review current capacity and protection settings with the responsible IT provider.
  3. Verify that protection covers both network-layer attacks and HTTP flood traffic.
  4. Check that monitoring can distinguish DNS amplification traffic and identify the new variants named in the report.

What changed since this was first reported: Cloudflare’s primary Q3 report provides the clearer update: hyper-volumetric attacks exceeding 1 Tbps fell to 251 in Q3 from 805 in Q2. The company associated the decline with law-enforcement action that dismantled four large IoT DDoS botnets, while warning that IoT botnets remain a high-volume threat.

Linux kernel: check MPTCP exposure and distribution fixes

Servers running Linux kernels dating back to version 4.4, including Ubuntu, Red Hat Enterprise Linux and Rocky Linux, are affected by CVE-2026-98432. The flaw is a use-after-free vulnerability caused by a race condition in TCP connection handling.

Researchers demonstrated unauthenticated remote code execution under specific conditions on servers with an MPTCP listener. The flaw can affect ordinary TCP connections, so include ordinary TCP connections in the exposure review.

  1. Check the Linux kernel advisory and the advisories for each distribution in use.
  2. Determine whether affected servers expose an MPTCP listener.
  3. Apply the available kernel update or mitigation to affected systems.
  4. Record the kernel version and remediation status for each server so later checks can verify the change.

What changed since this was first reported: The source supports the demonstration of remote code execution under specific conditions, but it does not state that every affected Linux server has been exploited.

ChatGPT shared links: use the fixed web frontend

Signed-in ChatGPT web users who opened a malicious shared link could have attacker code executed in their sessions, exposing private conversations and enabling actions through their accounts.

OpenAI reproduced the flaw, fixed both affected web frontend versions by October 26 and rated it P1. The researchers reported no real-world exploitation and said users needed to take no action.

  1. Confirm that the ChatGPT web frontend has updated to a fixed version.
  2. Avoid opening shared links from untrusted parties.
  3. Report suspicious links or suspected account activity through the appropriate IT or security channel.

What changed since this was first reported: The latest confirmed state provided by the source is that the issue was fixed by October 26 and no exploitation was reported.

Small-business triage for this briefing

  • Remote-access appliance users: Identify the asset owner, confirm whether Ivanti Connect Secure is deployed, check the installed version against the vendor advisory and record the patch and credential-rotation status.
  • Website owners: Ask the responsible IT provider which DDoS protections apply, whether network-layer and HTTP traffic are covered, and where monitoring results are recorded.
  • Windows and office users: Review the ChatGPT web frontend version and remind staff not to open untrusted shared links.
  • Linux-server operators: Check kernel and distribution advisories, confirm whether an MPTCP listener is present, apply the available update or mitigation and document the result.

Glossary

  • MPTCP: Multipath TCP.
  • BitLocker recovery key: A BitLocker recovery key.

FAQ

Which Ivanti Connect Secure versions are affected?

The report identifies versions 25.1.1.2 and prior and 22.8R2.5 and prior as affected. It lists patches in versions 25.1.1.3 and 22.8R2.6.

Does Binance say the stolen cryptocurrency affected user assets?

Binance said stolen wallets were covered and all user assets were safe. The source did not independently verify that assertion or state whether the remaining $3.3 billion was secured.

What should a small business do about the Linux kernel flaw?

Check the Linux kernel and distribution advisories, determine whether affected servers expose an MPTCP listener, and apply the available kernel update or mitigation.

BizScoreAI

BizScoreAI, which includes the free listing check

BizScoreAI scores how visible a business is to AI search and shows what its listing looks like to the engines people ask. Open the free listing check.

This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops. This is not financial, legal or investment advice.

Sources

← All Articles