r/SecOpsDaily • • 2d ago

The Microsoft outage wasn't an attack — and that's the interesting part for AppSec and AI security

0 Upvotes

Quick context since details are still settling: the Nov 12–13 Microsoft 365 outage (~18 hours, 70+ countries, Outlook/Teams/Exchange/Copilot) was caused by settings applied after a server update. The process that establishes secure connections got overwhelmed, servers stopped handling requests, and Microsoft rolled back a network configuration change. They've explicitly said no malicious/cyber activity and no AI agents involved.
Two threads I think are worth discussing beyond the usual "cloud is fragile" takes:

  1. Availability is a security property, and config changes are threat-model inputs.
    From an AppSec lens, this was a trusted change with a catastrophic interaction — functionally similar to a poisoned dependency or a compromised build pipeline, just without the adversary. If your threat model only considers what an attacker could do, you miss what your own deployment machinery can do to you. Two questions I'd want answered for any critical service path: what single config change could take it down, and do health checks fail gracefully or stampede a recovering system?

  2. AI tooling inherits the resilience of its substrate.
    Copilot went down with everything else, not because AI failed, but because it rides the same identity and control plane. Worth thinking about if you're building AI agent workflows: when the AI layer and the humans fall back to the same email/chat/identity backbone, you don't have a fallback at all. Also notable how quickly "this must be a breach" circulated in the first hours — when your incident response has to start by ruling out compromise, agent-driven noise on the same infrastructure makes that triage slower.
    Anyone done a genuine "blast radius of a trusted change" review for their stack? Curious what people found, especially around TLS/connection-heavy services.


r/SecOpsDaily • • 3d ago

WhatsApp sessions weaponised to distribute ValleyRAT

1 Upvotes

The in-memory payload, ValleyRAT (Winos 4.0), reads WhatsApp Desktop and WhatsApp Web session data, which is how one hijacked account becomes the next lure.

Our research and list of IoCs available here: https://lmntrix.com/blog/from-whatsapp-to-valleyrat-a-hijacked-contact-a-signed-citrix-binary-and-admin-rights-in-under-a-minute/


r/SecOpsDaily • • 3d ago

SecOpsDaily, are you okay?

17 Upvotes

It looks like /u/falconupkid has been banned and the sub-reddit has been taken over by bots. Unfortunate, because I was getting news from this sub 24 hours ago, and now I've gotta go back to individual websites.

Do I get to call RIP to this sub now? If yes, is there another sub that put together news like an RSS feed?


r/SecOpsDaily • • 3d ago

CVE-2026-119618 - Apache HTTP Server

Thumbnail
reddit.com
2 Upvotes

r/SecOpsDaily • • 5d ago

November 10 | 24h Recap: Chrome zero-day, GitHub secret theft and Qubole AWS breaches

Thumbnail
cyberrecaps.com
1 Upvotes

Three priorities from today’s recap:

  1. Chrome zero-day: Google patched CVE-2026-125350, an XML memory-safety flaw already exploited in attacks. Install the latest security update and relaunch the browser. Google has not disclosed the targets or attackers.

  2. Fake GitHub security audits: Socket’s October GhostAction investigation found malicious workflows stealing Actions secrets and credentials from repository files and Git history. Review unexpected workflow changes and rotate exposed credentials; deleting the file does not invalidate stolen keys.

  3. Qubole AWS access abused: Attackers used a Qubole-associated account to assume customer roles, including dormant integrations. Review CloudTrail from October 1, remove unused vendor access and investigate subsequent secret reads and S3 activity.

Read the full breakdown on CyberRecaps.


r/SecOpsDaily • • 5d ago

The Great Grocery Meltdown: What We Know About Europe’s Supermarket Refrigerator Hacks

Thumbnail reddit.com
1 Upvotes

r/SecOpsDaily • • 5d ago

The 2 Critical and 15 High CVEs fixed in Keycloak 26.8.2 explained in short

8 Upvotes

Hey there, I'm doing an analysis of the Critical and High CVE of Keycloak release for my job, and I thought it could also interest people in this community, so I'm sharing them here as well.

CVE-2026-111497 (9.2): The HTTP2Shell (also called Node2Shell) CVE in the Brotli decoder. Reachable in Keycloak if the experimental feature `http-client:v2` is enabled and Keycloak receives a malicious compressed response from a server it calls, such as an IdP. Exposure is therefore limited, but this could theoretically lead to a denial of service or arbitrary code execution. Workaround: disable `http-client:v2`.

CVE-2026-117691 (9.1): An issue in the SAML HTTP-Redirect binding implementation allowed an unauthenticated attacker to bypass the signature check of SAMLResponse, causing the server to process unsigned SAML messages and leading to full account takeover of federated users.

CVE-2026-97175 (8.8): An issue in the idp-auto-link authenticator (the "Automatically set existing user" option in the admin console), which handles user identity federation, let an attacker take over a victim's account. The attacker could use an email address that the provider had not verified to link their login to the victim's existing account.

CVE-2026-112208 (8.1): In realms using Organizations, an attacker belonging to several organizations could initiate a login and then switch to a registration or password reset path. A flag indicating successful login was not properly cleared, allowing the attacker to enter a victim's username and bypass authentication to gain full access to the victim's account and connected applications.

CVE-2026-114232 (8.1): An authenticated attacker who owns a User-Managed Access (UMA) resource could create a policy specifying a `resourceType` that would apply to all resources of that type, including ones belonging to other users, leading to unauthorized access to, or modification of, sensitive data.

CVE-2026-92857 (8.1): An authenticated attacker allowed to register clients through Dynamic Client Registration (with an Initial Access Token, for example) could create a malicious client application that forges identity information. They could configure their client to put a field they control, for example their first name, instead of their user ID in the access token. By changing their first name to another user's ID, they would be able to impersonate that user in other applications.

CVE-2026-96453 (8.0): When kcadm was used with a custom truststore, any self-signed certificate was accepted as long as the hostname matched, even if the certificate was not in your truststore. An attacker on the network path could pose as the Keycloak server and capture admin credentials sent by kcadm. The Keycloak server itself is not affected; update kcadm instead.

CVE-2026-103112 (7.5): An authenticated attacker could gain full access to a victim's account by using the forgotten password flow on the victim's account and logging in with their own account. This could trigger a race condition which could bind the attacker's session to the victim's account, allowing the attacker to change the victim's password.

CVE-2026-110932 (7.5): An unauthenticated attacker could send many requests with unique fabricated theme names, which would be stored on disk in the theme gzip cache. This could lead to disk space exhaustion that survives restarts, causing a denial of service.

CVE-2026-107123 (7.5): An unauthenticated attacker could send specially crafted SAML requests to the server containing excessively long dateTime or duration values that were not properly validated before processing. This could lead to high CPU utilization and a denial of service for all users.

CVE-2026-107602 (7.5): An unauthenticated attacker could send specially crafted SAML requests to cause threads processing a request to enter an infinite loop, leading to high CPU usage and a denial of service requiring a server restart.

CVE-2026-110931 (7.5): An unauthenticated attacker could send a specially crafted SAML request containing a specific element (`AuthorityBinding`) in an authentication statement. The parser could then enter an infinite loop consuming all available memory, causing the Keycloak service to crash and a denial of service.

CVE-2026-82965 (7.5): An unauthenticated attacker could send specially crafted large SAML XML messages to cause the server to consume excessive memory, leading to the application crashing and a denial of service.

CVE-2026-93998 (7.4): The Keycloak SAML adapter library (not the Keycloak server) verified the signature of SAML assertions, but failed to verify the issuer of the signed assertion. If multiple identity providers shared the same trusted signing key, an attacker controlling one of them could create validly signed assertions to log into the application as any user, including its administrators.

CVE-2026-92855 (7.4): In realms with a SAML identity provider that issues holder-of-key assertions (assertions bound to a key the user must prove they hold), Keycloak didn't check that proof. An attacker who intercepted a victim's signed assertion could replay it and impersonate the victim without needing their private key.

CVE-2026-97847 (7.1): An attacker with the `manage-clients` role could enable the service account of a client they manage and add a hardcoded-claim mapper that writes a realm administrator's identity into its tokens. Service account tokens have no session, so Keycloak resolved their owner from these claims and treated the attacker's token as the administrator's, giving them full control of the realm.

CVE-2026-96457 (High, no score yet): In realms using Fine-Grained Admin Permissions v2 and delegating group management to admins other than realm admins, an attacker with a delegated admin account allowed to manage at least one group could move this group to get around DENY rules set on subgroups, and therefore manage sensitive groups to get admin access to the realm.

If you have any ideas to make this more useful / readable, feel free to send them my way!


r/SecOpsDaily • • 5d ago

Tired of patching NetScaler every time a new CVE or KEV drops? Live walkthrough Nov 19

Post image
3 Upvotes

r/SecOpsDaily • • 6d ago

November 9 | 24h Recap: OpenSSH authentication bypass, SonicWall MFA evasion and LNbits shutdown

Thumbnail
cyberrecaps.com
1 Upvotes

Three items to prioritize from today’s recap:

  1. OpenSSH authentication bypass: SSHole is being exploited against vulnerable musl-based systems without PAM. Certain accounts can accept an invalid password when password authentication is enabled. Apply your distribution’s OpenSSH updates and restart sshd.

  2. SonicWall MFA bypass: Attackers with valid credentials for an alternate login method can bypass SAML authentication and potentially its MFA. Patch affected Gen7 and Gen8 firewalls, then investigate VPN sessions that lack matching identity-provider activity.

  3. LNbits emergency shutdown: The project expanded an extension-specific warning into a shutdown notice for all operators after attacks. Keep affected services offline and follow official patch and restart guidance.

Read the full breakdown on CyberRecaps.


r/SecOpsDaily • • 8d ago

After removing an exposed API key, how do you make sure it hasn't been used elsewhere?

Thumbnail reddit.com
1 Upvotes

r/SecOpsDaily • • 8d ago

November 7 | 24h Recap: OpenSSH exploitation, WordPress update exposure and Chainalysis stolen tokens

Thumbnail
cyberrecaps.com
1 Upvotes

Three updates worth prioritizing:

  1. OpenSSH bypass exploited: Attack attempts are hitting vulnerable musl-based Linux configurations without PAM. On affected Alpine systems, install the patched package and restart sshd. Updating the package alone leaves the running service exposed.

  2. WordPress update window: The first full-package update to a fixed release can still expose a temporary installer. Block web access to wp-content/upgrade/ before updating to 7.1.4 or your branch’s security release.

  3. Chainalysis credentials exposed: The company confirmed exposure of every user’s password hashes and live tokens. Its recovery process requires password resets and applicable API key rotation as access returns. Change reused passwords on other services too.

Read the full breakdown on CyberRecaps.


r/SecOpsDaily • • 8d ago

Chainalysis cyberattack exposed password hashes and live tokens for all users

Thumbnail reddit.com
2 Upvotes

r/SecOpsDaily • • 9d ago

We’re building open research on how AI agents get attacked, and we need people to review the data

Thumbnail
reddit.com
1 Upvotes

r/SecOpsDaily • • 9d ago

Siemens expands the device list for a 10.0-rated Node-RED flaw

Thumbnail
reddit.com
1 Upvotes

r/SecOpsDaily • • 9d ago

HostBadger -> Win hardening auditor / now with small GUI + enforcing profiles

1 Upvotes

**Hello! Some new features on HostBadger, a free, open-source Windows hardening auditor, now with a (not so) fancy GUI & remediation profiles**.

Nothing to install & in a few clicks, you'll see:

\-> **223 checks, each mapped to MITRE ATT&CK and explained**:

\- Credentials (LSA, Credential Guard, WDigest, NTLM)

\- Defender, ASR and EDR

\- BitLocker and Secure Boot

\- Network (SMB, LDAP, LLMNR, firewall, TLS, cleartext DNS)

\- RDP and WinRM

\- Accounts, UAC and LAPS

\- Privilege escalation (writable services and tasks, unquoted paths, PATH)

\- Logging and audit

\- Patching and end of support

\-> **Software**: EOL, versions behind the latest release, CVEs by installed version with CVSS/KEV/EPSS, vulnerable and malicious drivers (LOLDrivers), malicious browser extensions, remote access tools.

\-> **Threat hunting**: WMI/IFEO/COM persistence, hidden services and tasks (Tarrask), RID hijack, replaced accessibility tools, BITS jobs, Office hooks, suppressed event logs, hosts file, rogue root CAs.

\-> **Compliance**:

\- DISA STIG (1,475 rules, 14 products)

\- CIS, quoting each host's own benchmark numbers (Windows 11, Windows 10, Server 2016/2019/2022)

\- Essential Eight

\- NIS2 ACN for Italy

\-> **Report**: HTML dashboard, A–F score, trend over time and comparison with the previous run.

\-> **Fixes**: a reversible script under each check, Essential/Recommended/Strict profiles plus debloat and telemetry.

\-> **Optional AI summary** and prioritization hints (Gemini). Names are tokenized, and a leak check runs before anything is sent.

[https://github.com/g4bri-3l3/HostBadger/](https://github.com/g4bri-3l3/HostBadger/)


r/SecOpsDaily • • 10d ago

Title: Show HN: AI-Shield Pro – A 100% offline, zero-permission Android gateway preventing data leaks into ChatGPT ​Post Content: ​Hi everyone, As a 2nd-year Cybersecurity & IT undergraduate at University of Thamar, I built an on-device tool to solve the #1 vulnerability in generative AI (OWASP LLM0

Thumbnail reddit.com
1 Upvotes

r/SecOpsDaily • • 10d ago

Fiz uma série animada explicando Kubernetes do zero, do notebook até produção. Quero feedback técnico

1 Upvotes

Comecei um projeto paralelo chamado Ilustrando DevOps: vídeos curtos e animados que explicam infraestrutura montando o sistema peça por peça. Cada conceito só aparece quando resolve um problema da etapa anterior.

A primeira série é sobre Kubernetes, em 3 partes de ~1m30:

  1. Do Docker ao cluster: por que um servidor só não basta, Pods, Deployment, Service, Ingress e HPA

  2. Segurança: WAF no Ingress, movimento lateral e NetworkPolicy, Secret Manager (e por que Secret do K8s sozinho é só base64), hardening com Pod Security Admission e RBAC

  3. Dados e resiliência: PV/PVC, StatefulSet, antiafinidade, snapshot (réplica não é backup) e probes

O público-alvo é quem está começando em infra/SRE ou quem precisa explicar isso pra alguém do time.

Queria a opinião de vocês em duas coisas:

- Tem algo tecnicamente impreciso ou simplificado demais?

- Qual tema vocês gostariam de ver depois? (estou pensando em DNS, CI/CD ou VPN)

A série completa está no Instagram: https://www.instagram.com/ilustrandodevops/


r/SecOpsDaily • • 10d ago

Stopping Remote Code Execution (RCE) with Wasm Sandboxes

Thumbnail
reddit.com
1 Upvotes

r/SecOpsDaily • • 10d ago

EXPOSED: Upwork is actively ignoring malicious RCE malware targeting developers (Active Job & Repo Inside)

Thumbnail reddit.com
1 Upvotes

r/SecOpsDaily • • 11d ago

European supermarket freezer attacks: cross-source analysis of 11 reports (Danfoss / Copeland XWEB, two waves, attribution still open)

6 Upvotes

There has been a lot of scattered reporting on the refrigeration controller attacks in Europe, so to put some order into it and share the picture with the community, I cross-correlated 11 sources: CERT-FR, CSIRT-ITA/ACN, Copeland advisory, Censys x2, SentinelLABS, Claroty x2, The Record, Nextgov and BlackFog.

Timeline as it emerges from the sources

* Late Aug 2026: freezer disruptions at \~6 US military commissaries, suspected Iran-linked

* Oct 10-13: France, 350 to 700 stores, setpoints pushed up to \~50°C and forced defrost

* Oct 20-30: Lupovis reports credential spraying against Danfoss sensors, peak on Oct 26

* Nov 1-3: 100+ stores in 9+ countries (BE, SE, NL, LU, IE, EE, IT, PT, DE, anomalies in FI)

Where sources diverge

* Vector: Claroty’s Danfoss AK-SM 800A chain (CVE-2025-41450 + 41451, unauthenticated root) vs ANSSI’s assessment that France was mostly exposed interfaces plus weak/default credentials (`Admin`/`Admin` on XWEB). Censys shows 63.5% of exposed French hosts were on firmware < 4.2 on Oct 11, so both are plausible.

* Exposure vs contractor pivot: Censys/CERT-FR focus on directly exposed panels, while SentinelLABS and CSIRT-ITA point to shared third-party HVAC/R maintenance access (DE, PT).

* Attribution: nothing claimed or formally attributed. SentinelLABS lists CARR, Z-Pentest and NoName057(16) as leads, Nextgov reports Iran suspicion for the US commissaries, and copycats on the same weak attack surface can’t be excluded.

Other data points

* French exposed hosts dropped \~71% in 3 days after the CERT-FR alert. Patched and unpatched disappeared at the same rate, so operators pulled them offline rather than patching.

* Claroty had an AI coding agent reproduce the full unauth root chain on a lab unit in 28 minutes for about $6, using only public CVE text and firmware.

* XWEB EVO and Danfoss AK-SC are EoL with no patch path. In Belgium some units needed physical hardware changes.

* No malware, C2 or hashes have been published, so detection is mostly behavioral: off-hours logins (00:00-06:00), setpoint/defrost anomalies, alarm routing changes, admin lockouts, HMI vs independent probe discrepancies.

The full write-up has the detection notes, exposure queries, IoC/behavioral indicator tables and the ATT&CK (ICS + Enterprise) mapping, TLP:WHITE: https://ti-mindmap-hub.com/analytics/european-refrigeration-controllers-cold-chain-cross-source-analysis

Disclosure: I run the platform that produced the analysis, it’s an independent open-research project and not affiliated with my employer.

Curious what others are seeing. Has anyone observed contractor-side access in their own telemetry, or any activity on XWEB beyond default creds?


r/SecOpsDaily • • 11d ago

GitHub - kamehameha-ctrl/sniperscope: SniperScope is a high-performance External Attack Surface Management (EASM), passive/active OSINT intelligence, and forensic reporting workstation designed for cybersecurity auditors, SOC analysts, and penetration testers.

Thumbnail
github.com
1 Upvotes

r/SecOpsDaily • • 11d ago

Google warns hackers are literally draining cloud accounts down to zero with LLMjacking

Thumbnail reddit.com
1 Upvotes

Is this a thing?

Notes: Sorry if not the right sub. Yes im new here. Genuinely asking, not a bot. (Take an example: Am humanizing in a horizontal position, which is also human, on a human furniture upgrade as we speak.) Cheers


r/SecOpsDaily • • 11d ago

Escaping AWS Firecracker from guest userspace: VMM memory corruption (CVE-2026-122192)

Thumbnail
coinspect.com
1 Upvotes

r/SecOpsDaily • • 11d ago

Blindly clicking update / trusting the update path can itself be an attack surface...even the process of updating a vulnerable WordPress installation to a safe version can expose it to exploitation.

Thumbnail
xint.io
1 Upvotes

Autonmous pentesting platform Xint discovered a race in the WordPress core update process that leads to unauthenticated remote code execution, with WordPress sites that are manually updated particularly vulnerable

Something new to think about:
The way people typically frame vulnerability-hunting tasks can unintentionally cause LLMs to overlook certain classes of vulnerabilities. That is, when people ask an LLM to find vulnerabilities, they usually instruct it to find zero-days that work on the latest version.
However, this type of vulnerability is still a zero-day, even though it can't be triggered on the latest version at that moment. Since there's no newer version available to update to, the LLM often conclude