<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Securedotcom on Medium]]></title>
        <description><![CDATA[Stories by Securedotcom on Medium]]></description>
        <link>https://medium.com/@securedotcom?source=rss-1d50934ca651------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uCoPb8CLxQ_uimG79O-cDw.jpeg</url>
            <title>Stories by Securedotcom on Medium</title>
            <link>https://medium.com/@securedotcom?source=rss-1d50934ca651------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:39:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@securedotcom/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cisco Expressway Vulnerability Exploited Soon After Public PoC Drops]]></title>
            <link>https://medium.com/@securedotcom/cisco-expressway-vulnerability-exploited-soon-after-public-poc-drops-8d22436b8316?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d22436b8316</guid>
            <category><![CDATA[cisco]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 13:05:31 GMT</pubDate>
            <atom:updated>2026-11-20T13:05:31.267Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cisco Expressway Vulnerability Exploited Soon After Public PoC Drops</h3><ul><li><strong>Who should care:</strong> Anyone exposed to the Cisco Expressway vulnerability, meaning teams running Expressway-C or Expressway-E in a cluster on X15.5.3 or earlier.</li><li><strong>What could go wrong:</strong> An attacker with no login takes root on your video gateway, then moves into the rest of the network.</li><li><strong>Do this:</strong> Upgrade every node to X15.5.20 today and lock TCP 4371 and 4372 to cluster peers.</li><li><strong>Worth remembering:</strong> A patch nobody installs is just a press release.</li></ul><p>A <strong>Cisco Expressway vulnerability</strong> rated 9.8 has gone from advisory to active attack. Hackers used public exploit code to take root on four clustered gateways at a Russian organization. From there, they went shopping inside the network for passwords.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pe7l7cNg5sd-iF0fn7LFJQ.jpeg" /></figure><h3>What Happened?</h3><p>Cisco fixed CVE-2026–76466 on October 21. The bug sits in the cluster database service, which runs on Erlang and listens on TCP 4372. A maintenance identity and its cookie are hard-coded into the software and are the same on every install. As a result, anyone who can reach that port can join the cluster and run commands as <strong>root</strong> without a<strong> password</strong>.</p><p>Exploit code for the Cisco Expressway vulnerability landed on GitHub on November 5. On November 19, security firm F6 reported the first known attack. The intruders got into two internet-facing Expressway X15.5.3 boxes. From there, cluster trust carried them to two internal nodes that never touched the internet.</p><h3>What’s the Impact?</h3><p>Once inside, the attackers ran custom Python scripts that scanned for SMB shares, probed SQL Server and WinRM, and pulled credentials from internal GitLab repositories. F6 says the attackers also changed their scripts during the intrusion, and code comments suggest an AI assistant helped write them.</p><p>That makes this Cisco Expressway vulnerability more than an edge-device problem. A rooted gateway became a launch point into systems that should never have been reachable from the internet. Nobody has named the group behind it yet, and Cisco lists <strong>no workaround</strong>.</p><h3>How to Fix the Cisco Expressway Vulnerability</h3><ul><li><strong>Upgrade every cluster node</strong> to X15.5.20. X14 has no fix, so migrate off it.</li><li><strong>Allow TCP 4371 and 4372</strong> only from known cluster peers.</li><li><strong>Search your logs</strong> for <a href="https://www.secure.com/cdn-cgi/l/email-protection">[email protected]</a> and for Python files under /mnt/harddisk/.</li><li><strong>Check System &gt; Status</strong> for cluster peers you don’t recognize.</li><li><strong>Treat a hit as a breach:</strong> isolate the box, rotate secrets, and hunt for lateral movement.</li></ul><h3>Cisco Expressway Vulnerability Indicators of Compromise</h3><p>F6 published these indicators from the first confirmed intrusion. A hit is a lead, not proof, and a failed attempt may leave no trace.</p><ul><li><strong>IP addresses:</strong> 66.179.31[.]32 and 18.130.47[.]116</li><li><strong>Erlang node name:</strong> <a href="https://www.secure.com/cdn-cgi/l/email-protection">[email protected]</a> in erlang.log</li><li><strong>Staging path:</strong> /mnt/harddisk/i####[a-zA-Z]?/*.py (four digits, optional letter)</li><li><strong>Network:</strong> connections to TCP 4371 or 4372 from machines that aren’t cluster peers</li><li><strong>Public PoC:</strong> github[.]com/dinosn/cve-2026–76466</li></ul><p>So far, F6 has not shared file hashes or domains. In addition, the flaw was not in CISA’s Known Exploited Vulnerabilities catalog as of November 20, 2026.</p><h3>Your Edge Box Shouldn’t Be a Side Door</h3><p>About four weeks passed between Cisco’s fix and the first reported breach. For most teams, that gap is as much a staffing problem as a patching one. Secure.com’s <a href="https://www.secure.com/service-as-a-software">Service as a Software</a> model closes it: you hand over the outcome, and one team runs it.</p><ul><li><strong>Managed Exposure Management</strong> finds every clustered Expressway node you own, ranks each one by how reachable it really is, and confirms the fix landed.</li><li><strong>Offensive testing:</strong> our experts attack your perimeter the way this crew did, then harden what breaks and prove it’s closed.</li><li><strong>Managed SecOps</strong> watches around the clock for odd traffic to cluster ports and for gateways that suddenly start scanning SMB or SQL.</li><li><strong>A vCISO</strong> sets segmentation rules so one rooted edge device can’t reach GitLab.</li><li><strong>One service, one bill.</strong> No more grunt work. No more burnout.</li></ul><h3>Conclusion</h3><p>This Cisco Expressway vulnerability shows how quickly a fix becomes a race once exploit code is public. Patch every clustered node to X15.5.20, close ports 4371 and 4372 to everyone but cluster peers, and check your logs for the indicators above. Above all, if you find a hit, assume the attacker went further than the gateway.</p><h3>FAQs</h3><p>What is the Cisco Expressway vulnerability CVE-2026–76466?</p><p>It is a critical flaw, rated 9.8, in the cluster database service of Cisco Expressway-C and Expressway-E. A static cluster identity lets an unauthenticated attacker who can reach the service run commands as root. However, the flaw only hits clustered devices.</p><p>Is CVE-2026–76466 being exploited in the wild?</p><p>Yes. F6 reported on November 19, 2026, that attackers rooted four clustered Expressway X15.5.3 devices at a Russian organization, two weeks after exploit code appeared on GitHub.</p><p>Which Cisco Expressway versions are affected?</p><p>The flaw hits clustered Expressway releases X15.5.3 and earlier, and X15.5.20 fixes it. X14 and earlier have no fix, so Cisco recommends migrating to a fixed release.</p><p>Is there a workaround if I can’t patch right away?</p><p>Cisco lists no workaround. Until you can upgrade, F6 advises allowing TCP 4371 and 4372 only from trusted cluster node IP addresses.</p><p>How can I tell if my Expressway was compromised?</p><p>Search erlang.log for <a href="https://www.secure.com/cdn-cgi/l/email-protection">[email protected]</a>, look for Python files under /mnt/harddisk/, review cluster peers under System &gt; Status, and check for connections from 66.179.31[.]32 or 18.130.47[.]116. Treat any hit as a breach.</p><p><em>Originally published at </em><a href="https://www.secure.com/news/cisco-expressway-cve-2026-76466"><em>https://www.secure.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d22436b8316" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JPMorgan Data Breach: One Vendor Hack Exposes Visa and Mastercard Customers Too]]></title>
            <link>https://medium.com/@securedotcom/jpmorgan-data-breach-one-vendor-hack-exposes-visa-and-mastercard-customers-too-855da4715847?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/855da4715847</guid>
            <category><![CDATA[jpmorgan-chase]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 13:04:04 GMT</pubDate>
            <atom:updated>2026-11-20T13:04:04.432Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>November 20, 2026:</strong> The 48-hour clock ran out on Thursday, and the files went public. A ransomware crew called n0n has published customer data tied to JPMorgan Chase, Visa, and Mastercard after its ransom deadline passed. The <strong>JPMorgan data breach</strong> did not start inside JPMorgan. However, none of the three firms was hacked directly. Instead, their vendors were, and now their customers carry the risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytYjAPDMdv9CbKngDhf_pA.jpeg" /></figure><p>Who should care: Banks, card issuers, and any company that hands customer lists to a marketing, loyalty, or perks vendor.<br><strong>What could go wrong:</strong> A vendor you never audit leaks your customers’ contact details, and scammers send them convincing “card benefit” emails.<br><strong>Do this:</strong> List every vendor that holds your customer data this week, and revoke the long-lived access keys they hold.<br><strong>Worth remembering:</strong> Your own network can be clean while your customers end up on a leak site.</p><h3>What Happened in the JPMorgan Data Breach?</h3><p>n0n added all three firms to its leak site on November 16 with a 48-hour deadline. Nobody paid. As a result, the data went live on November 19.</p><p>At the center of the JPMorgan data breach is a file of about <strong>16,000 customer emails</strong>, some with phone numbers, account IDs and postal codes. Meanwhile, the Visa set covers <strong>more than 6,000 premium cardholders</strong> across nine Asia Pacific markets, with attached marketing campaign data. Finally, the Mastercard set has roughly <strong>2,000 badly formatted entries</strong> that may be test data.</p><p>In addition, a researcher found the same file layout in all three sets, which points to one <a href="https://www.secure.com/news/optimizely-supply-chain-attack">shared</a> <a href="https://www.secure.com/news/optimizely-supply-chain-attack">marketing supplier</a>. So far, nobody has named it.</p><h3>What They Said</h3><p>Visa blames a service provider in Asia Pacific and says no card numbers were affected. Similarly, Mastercard says a small group of cardholders in one benefit program had email addresses exposed. JPMorgan says attackers reached marketing data held by its vendors, and it will offer free credit monitoring. JPMorgan also says an unrelated Chase outage earlier in the week came from a software bug.</p><h3>Who Is n0n?</h3><p>n0n is the extortion group behind the JPMorgan data breach. It appeared in September 2026 and is believed to operate from Russia. In fact, researchers found no exploited software flaws in its campaigns. Instead, it gets in with <a href="https://www.secure.com/blog/cybersecurity/why-identity-is-the-primary-breach-vector">stolen passwords</a>, credential stuffing against FortiGate SSL VPN logins, and long-lived AWS keys left exposed. Earlier in November, it also claimed Expedia.</p><h3>What’s the Impact of the JPMorgan Data Breach?</h3><p>Based on what has been reported so far, the leak exposed <strong>no card numbers or passwords</strong>. Names, emails and account IDs still make a phishing email look real, though. For this reason, expect fake “Reserve concierge” and “card benefit” messages aimed at premium cardholders over the next few weeks, some quoting real account details.</p><h3>How to Avoid This</h3><p>The lesson here is that vendor access needs the same controls as your own systems:</p><ul><li><strong>Map your vendors.</strong> Record every vendor that holds customer data, which fields it keeps, and which staff can export them.</li><li><strong>Share less.</strong> Send marketing vendors only the fields a campaign needs, and mask account IDs.</li><li><strong>Lock down logins.</strong> Require MFA on vendor VPNs and admin consoles, and rotate long-lived cloud keys every quarter.</li><li><strong>Set a notice deadline.</strong> Write a 24-hour breach notification rule into vendor contracts.</li><li><strong>Warn customers early.</strong> Tell premium customers now that you will never email them to “verify” a benefit.</li></ul><h3>Your Vendor’s Weak Login Can Become Your Headline</h3><p>Notably, every firm here says its own systems were fine. That is the gap: customer data lives where your team never looks, and nobody tests it until a gang does.</p><p>Secure.com runs security as a service, so you get outcomes on one bill instead of another stack of tools:</p><ul><li><strong>Managed Exposure Management</strong> finds where your customer data sits outside your walls, flags exposed keys and weak vendor logins, then fixes them and proves the fix held.</li><li><strong>Managed SecOps</strong> watches around the clock for credential stuffing, unusual bulk exports, and leaked logins, and experts contain them before data moves.</li><li>vCISO gives you a senior security leader to set vendor data rules, run third-party reviews, and report vendor risk to the board.</li><li><strong>You set the rules, Secure.com does the work.</strong> Attack. Harden. Prove. Repeat.</li></ul><h3>JPMorgan Data Breach FAQs</h3><p>What happened in the JPMorgan data breach?</p><p>The extortion group n0n stole marketing data from a third-party vendor and leaked it on November 19, 2026, after a 48-hour ransom deadline passed. The leak includes about 16,000 JPMorgan Chase customer emails, plus data on Visa and Mastercard cardholders.</p><p>Were card numbers or passwords stolen?</p><p>No card numbers or passwords have been reported in the leak. Instead, the files hold names, email addresses, phone numbers, postal codes, and some account IDs.</p><p>Who is behind the attack?</p><p>n0n, an extortion group that appeared in September 2026 and is believed to operate from Russia. It breaks in with stolen or weak credentials, not software exploits.</p><p>What should affected customers do?</p><p>Treat unexpected emails about card benefits or concierge services with suspicion, and never confirm account details through a link in an email. If JPMorgan contacts you, accept the free credit monitoring it offers, and turn on MFA for your banking apps.</p><p>How can companies prevent a vendor data breach?</p><p>Map which vendors hold customer data, share only the fields each campaign needs, require MFA on vendor access, rotate cloud keys, and write fast breach notification terms into vendor contracts.</p><p><em>Originally published at </em><a href="https://www.secure.com/news/jpmorgan-data-breach"><em>https://www.secure.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=855da4715847" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitHub CI Secret Stealer Rides 4,837 Hijacked Accounts Into 61,000+ Repositories]]></title>
            <link>https://medium.com/@securedotcom/github-ci-secret-stealer-rides-4-837-hijacked-accounts-into-61-000-repositories-261a51d78f09?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/261a51d78f09</guid>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 10:03:43 GMT</pubDate>
            <atom:updated>2026-11-12T10:03:43.927Z</atom:updated>
            <content:encoded><![CDATA[<h3>GitHub CI Secret Stealer Rides 4,837 Hijacked Accounts Into 61,000+ Repositories</h3><ul><li><strong>Who should care:</strong> Every team that builds or ships through GitHub Actions, and anyone who has given a collaborator or bot a token with write access.</li><li><strong>What could go wrong:</strong> Every secret and cloud role your workflows can touch gets stolen, and the logs that would prove it are deleted.</li><li><strong>Do this:</strong> Search your repos for the probe pull request and commit titles below, then look for missing run numbers in the Actions tab.</li><li><strong>Worth remembering:</strong> Rotating keys won’t evict an attacker who has already planted a backdoor in AWS or Azure.</li></ul><h3>Introduction</h3><p>A new wave of stolen GitHub logins is turning <a href="https://www.secure.com/blog/appsec/github-supply-chain-attacks-explained">CI pipelines</a> into credential vacuums. Since November 10, the GitHub CI secret stealer has used <strong>4,837</strong> hijacked accounts to probe <strong>61,764</strong> repositories. At least <strong>1,806</strong> of them have already leaked their secrets, according to Aikido Security.</p><h3>What Happened in the GitHub CI Secret Stealer Attack?</h3><p>Each attack starts with a harmless-looking pull request, <strong>“docs: dependency audit notes,”</strong> that only tests for write access. Where the stolen token can write, the attacker pushes a roughly 1,500-line shell stealer. It is usually tucked into an existing workflow under the commit <strong>“ci: refresh build cache.”</strong> Other copies hide in a new workflow or in a script wired to an npm postinstall hook.</p><p>After the job runs, the change is reverted within minutes, and the run and its logs are deleted. StepSecurity counted more than <strong>21,000</strong> injection commits in two days. On November 12, new copies switched from two exfiltration IPs to a Telegram chat, as SafeDep reported.</p><h3>What’s the Impact?</h3><p>The stealer takes every Actions secret, the workflow token, <a href="https://www.secure.com/news/one-npm-package-one-developer-full-cloud-wipeout-in-72-hours">OIDC tokens</a>, and secrets held in runner memory. It trades the OIDC tokens for AWS, GCP, and Azure sessions and opens IAM trust policies to anyone.</p><p>It also adds Azure federated credentials that keep working after you rotate secrets. That turns the GitHub CI secret stealer from a one-time leak into lasting cloud access. At least <strong>50</strong> victims publish npm, Go, Packagist, PyPI, or crates packages, so the damage can spread to everyone downstream.</p><p>Accounts hit in October’s GhostAction wave were about <strong>1,000 times</strong> more likely to be reused this week, The Hacker News reported. In more than 100 repos, the new stealer was added on top of October’s leftover workflow. Researchers haven’t tied the two campaigns to one actor, but the lesson is the same: secrets nobody rotated became the next way in.</p><h3>How to Avoid the GitHub CI Secret Stealer</h3><ul><li><strong>Search your org</strong> for the probe title and for the commits “ci: refresh build cache,” “chore: add ci helper,” and “chore: add dependency audit workflow.” A gap in run numbers right after one of them means the stealer probably ran.</li><li><strong>Assume theft if it ran.</strong> Treat every secret, variable, and cloud role that workflow could reach as stolen. Also revoke the commit author’s tokens, sessions, and SSH keys.</li><li><strong>Hunt cloud backdoors.</strong> Look for IAM roles that trust any principal, unexpected new access keys, and Azure federated credentials with a “wfx” prefix.</li><li><strong>Lock down egress.</strong> Use an allowlist to block bare IPs and api.telegram.org from CI runners.</li><li><strong>Shrink standing access.</strong> Replace stored cloud keys with tightly scoped OIDC roles, and require code owner review on every change under .github/workflows.</li></ul><h3>GitHub CI Secret Stealer Indicators of Compromise (IOCs)</h3><p>Researchers published network, commit, file and cloud indicators for this campaign. A hit on any of them in a repo you can write to, dated November 10 or later, means the account and every secret that workflow could reach should be treated as compromised.</p><h3>Attack Your Pipeline Before a Stolen Token Does</h3><p>This campaign worked because nobody was watching who changed workflows or what those workflows could reach. Secure.com’s AI teammates attack your pipeline first, harden what they find, and prove the fix, while your team sets the rules.</p><ul><li>Flags workflow changes from accounts and bots that have never touched CI before</li><li>Maps which secrets and cloud roles each workflow can reach, so the blast radius is clear in minutes</li><li>Catches open trust policies, rogue access keys, and unknown federated credentials across AWS and Azure</li><li>Runs credential rotation as a governed playbook your team approves, with an audit trail for every step</li><li>Tests runner egress the way an attacker would, then gives your team the fix</li></ul><p><strong>Attack. Harden. Prove. Repeat.</strong></p><h3>Conclusion</h3><p>The GitHub CI secret stealer didn’t need a zero-day. It needed stolen logins, workflows nobody watched and secrets nobody rotated after October. Search for the commit titles, check your run numbers, and clean out your clouds before you call the incident closed.</p><h3>FAQs</h3><p>What is the GitHub CI secret stealer?</p><p>It is a campaign that began on November 10, 2026. Attackers used 4,837 hijacked GitHub accounts to push a roughly 1,500-line shell script into GitHub Actions workflows. The script steals every secret the workflow can reach, sends it out, then reverts the change and deletes the run logs.</p><p>How do I know if my repository was hit?</p><p>Search for the probe pull request “docs: dependency audit notes” and the commits “ci: refresh build cache,” “chore: add ci helper,” “chore: add dependency audit workflow,” “ci: restore,” or “ci: cleanup.” A missing run number in the Actions tab right after one of them is the strongest sign the stealer ran.</p><p>Is this the same as October’s GhostAction campaign?</p><p>Not confirmed. Accounts hit by GhostAction were about 1,000 times more likely to be reused, and in more than 100 repos the new stealer sat on top of October’s leftover workflow. Researchers have not tied the two campaigns to one actor.</p><p>Is rotating secrets enough to recover?</p><p>No. The stealer can open IAM trust policies, create new access keys, and add Azure federated credentials named wfx-ci-. Those keep working after rotation, so you also need to find and remove them.</p><p>Which packages were affected?</p><p>Packagist digitalelvis/neuronai-studio 3.14.3 is malicious, so anyone who installed it should treat that machine as compromised. The Go modules onuragtas/docker-env (v1.0.278 and v1.0.280) and vkuznet/gocurl carry the payload only in workflow files. More than 50 compromised users publish packages to npm, Go, Packagist, PyPI, or crates.</p><p><em>Originally published at </em><a href="https://www.secure.com/news/github-ci-secret-stealer"><em>https://www.secure.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=261a51d78f09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHP2Shell: How to Prove the Patch Actually Took Effect]]></title>
            <link>https://medium.com/@securedotcom/php2shell-how-to-prove-the-patch-actually-took-effect-3c9d77b9a8d1?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c9d77b9a8d1</guid>
            <category><![CDATA[php2shell]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 07:31:14 GMT</pubDate>
            <atom:updated>2026-10-23T07:37:39.369Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Seven hours after PHP shipped the emergency fix for PHP2Shell, a public scan of roughly 606,000 internet-facing services on supported PHP branches found 2,149 running a patched version. That is 0.36%. The patch was free, the advisory was everywhere, and almost nobody had it running yet.</p><h3>TLDR</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oOPuOs53oVp8YMFN47btEg.jpeg" /></figure><p>PHP2Shell is the nickname for CVE-2026–109618 and CVE-2026–109619, two memory safety flaws in the PHP engine that both score 9.2 on CVSS v4. Updating the package is the easy half. The fix takes effect only after every PHP worker restarts, and a package scanner cannot see inside a running worker. This post covers the five places a PHP patch quietly fails, the six checks that settle it, and what to write down so the answer survives your next deploy.</p><h3>Why “we patched it” is not an answer</h3><p>Patching PHP writes new files to disk. It does not touch processes that are already running. A worker that started before the upgrade keeps serving the code it loaded at startup, and it will keep doing that until something restarts it.</p><p>That means two servers can report the same version and have completely different exposure. One restarted its pools. One did not.</p><p>PHP says it plainly: updating is the only complete fix, and no configuration change makes an installation safe. Memory limits and the session upload progress setting reduce one path each. Neither is remediation.</p><h3>Five places a PHP patch quietly fails</h3><p>PHP2Shell · Patch verification</p><h3>Five places a PHP patch quietly fails</h3><p>Each one leaves the package database saying you are fixed. Each one has a check that settles it.</p><p>Every one of these leaves your package database saying you are fixed.</p><h3>1. The worker never restarted</h3><p>FPM pools and Apache children survive a package update. Until you reload or restart the service, the workers keep serving the old build.</p><h3>2. You checked the shell, not the site</h3><p>FPM reads its own pool configuration rather than the command line settings. So a terminal check can show a patched version while the site still serves the old one. The version that matters is the one a served request reports.</p><h3>3. The host runs more than one PHP</h3><p>Hosting panels and multi-site servers commonly keep several branches installed. A patched 8.2 does nothing for a site still routed to an 8.1 pool. CMS fleets collect orphaned PHP versions nobody owns.</p><h3>4. The image was never rebuilt</h3><p>A running container keeps the PHP it was built with, so updating the base image alone changes nothing. Patch the container, and the image in your registry is still exposed, waiting for the next deploy.</p><h3>5. The version number is lying</h3><p>Distribution backports fix the code and keep the old version string. This cuts both ways. A server reading 8.1.33 may be fixed, and a server reading a higher number may not be. Trust the package changelog, not the banner.</p><h3>Six checks that settle it</h3><ul><li>Read the version from a request PHP actually served, not from a shell.</li><li>Search the package changelog for both CVE IDs rather than comparing version numbers.</li><li>Compare worker process start time against package install time on every pool.</li><li><a href="https://www.secure.com/blog/infrastructure-security/agentless-asset-vulnerability-discovery">List every PHP branch</a> installed on the host, then confirm which binary each site is routed to.</li><li>Rebuild container images from a patched base, redeploy, then confirm the orchestrator rolled the new image.</li><li>Re-test the exposed surface from outside against a target you own.</li></ul><h3>Why the honest test is disruptive</h3><p>Here is the part most remediation guides skip. The definitive external test for<a href="https://www.secure.com/news/php2shell-php-rce-focus-keyphrase"> PHP2Shell sends a large payload </a>designed to exhaust worker memory. It can crash a worker and interrupt live requests.</p><p>So the only test that truly proves the fix carries a real cost. Published guidance says to run it outside peak hours, and that a clean result from a passive checker does not confirm you are patched.</p><p>This is why patch verification is a governance problem, not just a technical one. Somebody has to decide which production hosts get tested, inside which window, and who can stop the run. Without that, teams skip the test and write patched in the ticket.</p><h3>What to write down</h3><p>A patch ticket closes. An evidence record stays open until something proves it wrong. For each host or image, record the fixed version and how you confirmed it, the restart time, the web served version, whether the host is reachable from outside, what you tested and what you did not, any observed probe activity with its time window, the owner of the next action, and what would invalidate the record.</p><p>Any field may say unknown. It then has to name the missing evidence.</p><p>A worker restart is a deployment change, so the next deploy should send the record back to recheck required rather than leaving it green. <a href="https://www.secure.com/blog/cybersecurity/risk-based-vulnerability-management-fix-first-list">For hosts you cannot patch yet</a>, write the compensating control and an approved exception with an expiry date.</p><p>What a verified host looks like on paper</p><h3>Nine fields, and “unknown” is a legal answer</h3><p>A patch ticket closes. An evidence record stays open until something proves it wrong. Here is one host, written the way an auditor or a board can read it.</p><h3>Who goes first</h3><ul><li>Apache servers running mod_php are the worst case because the attack reaches the engine before a single line of application code runs. PHP rates that setup as highest risk, and one scan counted at least 565,000 public services using it.</li><li>Internet-facing Linux web servers with no endpoint monitoring come next. A successful run is reported as near-silent: the worker doesn’t crash, and the response looks normal, so there may be nothing in the application log to find later.</li><li>Shared hosting and multi-tenant panels follow, because one missed pool affects every site on the box.</li><li>End-of-life branches are a project, not a patch. PHP 8.1 and older get no official fix, so the choices are a vendor backport, a migration, or isolating the host while you plan one.</li></ul><h3>Patched? Prove it.</h3><p>Verification is paperwork nobody budgets for, and it lands on the same people who just spent a night patching.</p><ul><li>Secure.com Red Teaming retests your exposed PHP surface after you patch, inside a scope your team signs and can stop mid-run.</li><li>The one-target scan at $5,000 includes a 30-day verification re-scan, so proving the fix isn’t a second purchase.</li><li>CSPM Teammate maps the attack path on your public hosts once your scanner reports the finding and the NVD record lands, with no wait for a KEV listing.</li><li>Response workflows hold for a named approver in Slack or Teams before anything restarts, isolates, or rotates.</li><li>Every run leaves one record per host: what was tested, what was not, and what is still unknown.</li></ul><p>Your team sets the rules. The teammates do the work. Attack. Harden. Prove. Repeat.</p><h3>FAQs</h3><p>How do I check if PHP2Shell is actually patched on my server?</p><p>Two checks together. Search your package changelog for CVE-2026–109618 and CVE-2026–109619, because a backport can fix the code without changing the version number. Then read the PHP version from a request the web server actually served, not from a command line, since FPM runs its own configuration.</p><p>Is restarting PHP enough, or do I need to reboot the server?</p><p>A service restart is enough, as long as it covers every FPM pool and the web server itself. Published guidance uses the terms reload or restart. Restart is the one with no ambiguity, because it guarantees no child process predates the upgrade.</p><p>My PHP version number did not change after the update. Am I still vulnerable?</p><p>Possibly not. Distribution maintainers often backport a security fix and keep the existing version string, so the number stays the same while the code is fixed. The changelog is the answer, not the banner.</p><p>Can a free online PHP2Shell checker confirm my site is safe?</p><p>No. A clean result from a passive checker does not confirm you are patched, and the definitive test sends a payload that can crash a worker. Treat an online checker as a first pass, then verify on the server and schedule a real retest.</p><p>Do I need to rebuild my container images, or is patching the running container enough?</p><p>Rebuild. A running container keeps the PHP it was built with, and patching inside it leaves the image in your registry exposed. The next deploy will reintroduce the old runtime.</p><p><em>Originally published at </em><a href="https://www.secure.com/blog/cybersecurity/php2shell-patch-verification"><em>https://www.secure.com</em></a><em> on October 23, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c9d77b9a8d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHP2Shell Leak Forces Early Patch, Putting Most of the Web at Risk]]></title>
            <link>https://medium.com/@securedotcom/php2shell-leak-forces-early-patch-putting-most-of-the-web-at-risk-c47d7728f898?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/c47d7728f898</guid>
            <category><![CDATA[php2shell]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 07:31:11 GMT</pubDate>
            <atom:updated>2026-10-23T07:31:11.622Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Decade-Old PHP Bug That AI Finally Made Easy to Exploit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*07ZXULMkLvAK50VlCO0AqA.jpeg" /></figure><p>The patch was due Thursday, October 22. A leak on Tuesday changed that. On October 20, the two CVE IDs began circulating online with the wrong release time and an inflated CVSS score of 10.0, so the PHP project moved the release up by a day. Fixed builds landed on October 21.</p><p>Researchers independently traced multiple memory-safety bugs in the PHP engine to a shared root cause in how PHP handles out-of-memory errors. They are tracked as <a href="https://www.cve.org/CVERecord?id=CVE-2026-109618">CVE-2026–109618</a> and CVE-2026–109619, rated up to CVSS 9.2. Because the bugs live below the application layer, even a “Hello World” app on an affected version can be vulnerable.</p><p>The worst case is Apache with mod_php, where an unauthenticated request can reach code execution with default settings before any application code runs.</p><h3>What Happened?</h3><p>Researchers found two memory-safety bugs inside the PHP engine itself. They are now tracked as CVE-2026–109618 and CVE-2026–109619, and both carry a <a href="https://www.secure.com/blog/risk-and-governance/cvss-scores-not-risk-scores">CVSS score of 9.2.</a> Because the bugs live below the application layer, a site with perfectly clean code can still be taken over.</p><p>Nearly every PHP release since version 5.4 is affected. Details slipped out publicly on October 20, a day before the embargo was set to lift, so the PHP team pulled its release forward. Fixed builds landed on October 21. Attack attempts showed up within hours.</p><h3>What’s the Impact?</h3><p>PHP powers roughly 69% of the websites whose server-side language is known. A working attack hands an intruder code execution as the web worker account, plus the ability to read passwords, session tokens, and API keys straight from server memory. One honeypot network recorded an exploit attempt on October 17, four days before anyone outside the disclosure group was supposed to know.</p><p>That detail is the real story here. The vulnerable code sat untouched for more than a decade because chaining it into a working exploit was brutally hard. The research team says frontier AI models collapsed that effort from months to days. The same compression now works for whoever is reading the patch notes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*9Qz_y2LRlZz0cOlx.gif" /></figure><h3>How to Avoid This</h3><ul><li><a href="https://www.secure.com/blog/cloud-security/vulnerability-remediation-best-practices">Patch today</a> to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35</li><li>Check unsupported builds, since minimal source backports exist for 7.4, 8.0, and 8.1</li><li>Hunt for PHP worker processes spawning shells or download tools</li><li>Rotate credentials, tokens, and keys that lived in server memory</li><li>Do not lean on the session upload progress toggle as your only cover</li></ul><h3>Indicators of Compromise</h3><p>Published indicators are thin so far, and most of what is circulating is behavioral rather than a clean hash list. Threat researchers have shared a small set of source addresses tied to early exploit attempts, along with request-level and host-level signals worth hunting. One caution before you reach for a block rule: those addresses belong to shared anonymization infrastructure, so treat a hit as a reason to investigate, not proof of compromise.</p><p>Indicators of Compromise · PHP2Shell</p><h3>What to hunt for while you finish patching.</h3><p>Published indicators are still thin. Most of what is useful right now is behavioral. Start with the request signal, then pivot to the host.</p><p>Observed in honeypot telemetry</p><p>Web and proxy logs</p><p><strong>Before you write a block rule:</strong> the addresses above sit on shared anonymization infrastructure. Treat a hit as a reason to open an investigation, not as proof of compromise. Exploitation can also succeed without crashing the worker, so crash logs alone will miss it.</p><h3>Your Patch List Is Long. Your Attacker’s List Is Short.</h3><p>Every exposed server is now in a footrace between a patch window and an exploit that already works. PHP2Shell matters. The harder question is which of your assets an attacker can actually reach today.</p><ul><li>Red AI Teammate attacks your own exposed surface and confirms what is genuinely exploitable, not just what scanners flag</li><li>Cloud Security AI Teammate maps exposed PHP workloads so the patch list follows reachability, not CVSS alone</li><li>AppSec AI Teammate routes the fix to the owner who can ship it and validates the build afterward</li><li><a href="https://www.secure.com/soc-operations-teammate">SOC AI Teammate</a> hunts the behavioral signals in your logs and assembles the case before anyone pages you</li><li>Every consequential action waits for your approval, and every step leaves an evidence trail you can show an auditor</li></ul><p>Attack. Harden. Prove. Repeat.</p><p><em>Originally published at </em><a href="https://www.secure.com/news/php2shell-php-rce-focus-keyphrase"><em>https://www.secure.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c47d7728f898" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is Cybersecurity Awareness Month? 2026 Themes, Dates, and What It Means for Security Teams]]></title>
            <link>https://medium.com/@securedotcom/what-is-cybersecurity-awareness-month-2026-themes-dates-and-what-it-means-for-security-teams-28c4003a63c3?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/28c4003a63c3</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 13:18:20 GMT</pubDate>
            <atom:updated>2026-10-12T08:05:07.223Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR</strong>: Cybersecurity Awareness Month runs October 1 to 31 every year. It started in 2004 and is co-led by CISA and the National Cybersecurity Alliance. In 2026, it has two official themes, one from each organization, which is why you keep seeing different slogans. The four habits it teaches still work. What’s changed is the speed and volume on the attacker side, so security teams need a plan for attacks that never touch an employee.</p><h3>Introduction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-_xjFl4tn6M7kxvnPix3A.jpeg" /></figure><p>In this year’s Verizon Data Breach Investigations Report, software vulnerabilities surpassed stolen passwords as the top entry point, at 31% of breaches. A third party was involved in 48% of breaches, up 60% in a single year. October is when most companies talk about all of this. Then November arrives, and the posters come down.</p><p>October 2026 · Cybersecurity Awareness Month</p><h3>Two official themes. One October.</h3><p>The two organizations that co founded the campaign published different wording this year. Knowing which belongs to which saves an awkward correction in front of your exec sponsor.</p><p>Source: CISA and National Cybersecurity Alliance, October 2026</p><h3>What is Cybersecurity Awareness Month?</h3><p>Cybersecurity Awareness Month is a global campaign held every October. The Cybersecurity and Infrastructure Security Agency (CISA) and the National Cybersecurity Alliance (NCA) co-lead it. Governments, companies, and schools use the month to push a small set of security habits to employees and the public. 2026 marks the 23rd year.</p><h3>When is Cybersecurity Awareness Month?</h3><p>October 1 to 31, every year. There is no fixed weekly structure, so most organizations build their own four-week plan around whichever theme they pick.</p><h3>What is the Cybersecurity Awareness Month 2026 theme?</h3><p>There are two in 2026, published by the two organizations that co-founded the campaign. If you’ve seen conflicting slogans, that is why.</p><h3>CISA 2026 theme: Securing the Next 250</h3><p>CISA is running “Securing the Next 250,” tied to the United States’ 250th anniversary. It targets critical infrastructure operators and their suppliers and asks them to practice what CISA calls the 3Rs: Reduce, Replace, Recover.</p><h3>NCA 2026 theme: Don’t Make It Easy for Them</h3><p>The National Cybersecurity Alliance is running “Don’t Make It Easy for Them.” Its 2026 toolkit uses real cases of scammers who were arrested or shut down to illustrate four threats: password cracking, unprotected accounts, unpatched systems, and phishing. The message is that attackers pick easy targets.</p><h3>Which theme should you run?</h3><p>Pick CISA’s if you operate or supply critical infrastructure, because the material is written for that audience. Pick the NCA’s if your October campaign targets employees. Whichever you quote, name the organization next to it so nobody has to guess.</p><h3>Why people still call it National Cybersecurity Awareness Month</h3><p>It used to be called National Cybersecurity Awareness Month. The campaign dropped “National” as participation spread outside the United States. Both names refer to the same October campaign, so search results and toolkits still mix them.</p><h3>When did October Cybersecurity Awareness Month start?</h3><p>It started in October 2004, created by the U.S. Department of Homeland Security and what was then the National Cyber Security Alliance. Early advice was as basic as updating antivirus software twice a year. The campaign has run every October since.</p><h3>The four habits the campaign asks for</h3><p>Cyber hygiene does most of the work in security, and the campaign’s core advice has stayed consistent for years:</p><ul><li>Use long, unique passwords and a password manager</li><li>Turn on multifactor authentication, and use phishing-resistant MFA where you can</li><li>Learn to recognize and report phishing</li><li>Install software updates promptly</li></ul><p>CISA adds four more for organizations: turn on logging, back up your data, encrypt it, and report incidents so other defenders get the warning. None of this is new. Most breaches still involve skipping at least one of these.</p><h3>What changed in 2026</h3><p>The habits still hold. The conditions around them moved.</p><h3>Attacks now run at machine speed</h3><p>Attackers automated the slow parts. Hoxhunt’s detection network, which monitors more than four million users, logged AI-generated phishing jumping from about 4% of reported phishing in November 2025 to 56% in December, settling near 40% in January 2026. Treat the exact figures as directional and the direction as clear. The spelling mistakes and odd phrasing that awareness training taught people to spot are gone.</p><h3>Ransomware operates like an industry</h3><p>Ransomware appeared in 48% of breaches in the 2026 DBIR, up from 44%. Its share has never gone down in any edition of the report. The economics are shifting, though: 69% of victims refused to pay, and the median payment fell to about $139,875. Attackers have responded by running the pipeline earlier, with 73% of ransomware victims showing an infostealer infection or credential leak in the year before the attack.</p><h3>More connections mean more surface</h3><p>Every new SaaS tool, cloud account, API, and AI integration adds another entry point for an attacker. The DBIR found only 26% of vulnerabilities in CISA’s Known Exploited Vulnerabilities catalog were fully remediated in 2025. These are flaws confirmed to be under active attack, published in a free public list, and three-quarters of them stayed open.</p><h3>Suppliers became the way in</h3><p>Third-party involvement reached 48% of breaches, up 60% from 30% a year earlier. Verizon traces most of the headline incidents to plain authentication failures at the vendor: missing MFA, stale credentials, no least privilege. An annual vendor questionnaire does not catch any of that.</p><h3>Quantum is a timing problem, not a future one</h3><p>Attackers are already collecting encrypted data to decrypt later, once quantum computers can break current math. NIST’s transition plan deprecates RSA 2048 and ECC P-256 by 2030 and removes quantum-vulnerable algorithms from its standards by 2035. If your data stays sensitive past those dates, the clock started when it left your network.</p><p>Verizon DBIR 2026 · 22,000+ breaches</p><h3>Awareness covers the people. Look where breaches start.</h3><p>Four numbers from this year’s Verizon Data Breach Investigations Report, which analyzed more than 22,000 confirmed breaches across 145 countries.</p><p>Source: Verizon Data Breach Investigations Report 2026</p><h3>Why the answer to AI risk involves AI</h3><p>Defenders cannot read 3,000 alerts a day by hand while attackers generate attacks by the thousand. In the WEF Global Cybersecurity Outlook 2026, 94% of respondents named AI as the biggest driver of change in security this year, and 77% of organizations already use AI somewhere in their security work.</p><p>The hesitation is about control, not capability. The same report lists the top barriers to adopting AI in security as missing knowledge and skills (54%), the need for human oversight (41%), and uncertainty about risk (39%). Security teams will hand work to AI. They will not hand over decision rights.</p><p>That distinction is the whole design question. AI that only advises leaves the work with your analyst. AI that acts without boundaries creates a problem you cannot explain to an auditor. AI that acts inside scope you define, with approval gates on consequential steps and a logged trail, gets work done and stays defensible.</p><h3>When to bring in outside help</h3><p>Most mid-sized teams can find a problem. Fewer can find it, fix it, prove the fix, and still run the day job. The WEF report found that among organizations reporting weak cyber resilience, 85% also said they lacked critical security skills and people. Small organizations reported insufficient expertise at 46%, against 29% for large ones.</p><p>Two questions worth answering before the month ends. If you were breached tomorrow, who recovers your systems, and how long would it take? And is anything checking your exposure between audits, or does an attacker get to find it first?</p><h3>How Secure.com helps</h3><p>Secure.com runs governed AI teammates above the stack you already own. They attack your defenses, harden what they find, and give your team back hundreds of hours a month, inside scope and approvals you set.</p><ul><li>The <strong>Red Teammate</strong> tests your environment continuously inside an approved scope, so exposure is found between audits rather than during them</li><li>The <strong>SOC Teammate</strong> handles triage, enrichment, and case assembly, which cuts the queue that makes real alerts easy to miss</li><li>Offensive findings feed defensive work automatically, so what is exploitable gets fixed first instead of landing in another backlog</li><li>Consequential actions stop at a human approval gate, and every recommendation, approval, and action is logged for your auditor or board</li><li>It starts with one teammate on one function, works above your existing tools, and goes live in days</li></ul><p>Your team sets the rules. AI teammates do the work.</p><h3>A four-week plan for October</h3><p>Attack. Harden. Prove. Repeat.</p><ul><li><strong>Week 1, attack:</strong> run a scoped test against your own people and your own exposed surface</li><li><strong>Week 2, harden</strong>: fix what carries a real exploit path first, starting with KEV items and vendor accounts missing MFA</li><li><strong>Week 3, prove: </strong>rerun the same test, record the before and after state, keep the approval trail</li><li><strong>Week 4, repeat: </strong>put the cycle on the calendar for the other eleven months</li></ul><p>A four week plan for the security team</p><h3>Attack. Harden. Prove. Repeat.</h3><p>Posters and quizzes cover the people. These four weeks cover the systems, and they leave you with evidence instead of a completion rate.</p><p>Control Your team sets the rules. AI teammates do the work.</p><h3>How to measure whether it worked</h3><p>Completion rates measure attendance. These measure behavior:</p><ul><li><strong>Reporting rate:</strong> what share of simulated phishing gets reported, not just avoided</li><li><strong>Time to report:</strong> how many minutes pass between delivery and the first report</li><li><strong>Repeat clicker rate: </strong>the same small group usually drives most of the risk</li><li>Mean time to respond on employee-reported incidents</li><li>Percentage of KEV listed vulnerabilities closed during the month</li></ul><h3>Free resources and toolkits</h3><p>CISA publishes a free Cybersecurity Awareness Month toolkit with posters, sample emails, a press release template, slide decks, and social copy. The National Cybersecurity Alliance publishes its own toolkit built around the 2026 theme. Both are free, and both save you from designing October from scratch.</p><h3>FAQs</h3><p>What is Cybersecurity Awareness Month?</p><p>It is a global campaign held every October, co-led by CISA and the National Cybersecurity Alliance. It promotes a small set of security habits to employees and the public. 2026 is its 23rd year.</p><p>When is Cybersecurity Awareness Month 2026?</p><p>October 1 to 31, 2026. The campaign runs the full month, and organizations usually split it into four weekly themes of their own.</p><p>What is the Cybersecurity Awareness Month 2026 theme?</p><p>There are two. CISA is running “Securing the Next 250,” focused on long-term resilience for critical infrastructure. The National Cybersecurity Alliance is running “Don’t Make It Easy for Them,” focused on everyday habits.</p><p>When did Cybersecurity Awareness Month start?</p><p>October 2004. It was created by the U.S. Department of Homeland Security and the National Cyber Security Alliance, and it was originally called National Cybersecurity Awareness Month.</p><p>How should a security team prepare for Cybersecurity Awareness Month?</p><p>Run a scoped test in week one, fix what the test exposes in week two, retest and record the evidence in week three, and schedule the same cycle for the rest of the year in week four. Report reporting rate and time to report rather than training completion.</p><p><em>Originally published at </em><a href="https://www.secure.com/blog/cybersecurity/what-is-cybersecurity-awareness-month"><em>https://www.secure.com</em></a><em> on October 6, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28c4003a63c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attackers Are Inside the Mail Gateway: FortiMail Zero-Day Exploited Before a Patch Exists]]></title>
            <link>https://medium.com/@securedotcom/attackers-are-inside-the-mail-gateway-fortimail-zero-day-exploited-before-a-patch-exists-bb9387c33275?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb9387c33275</guid>
            <category><![CDATA[fortimail]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 11:12:27 GMT</pubDate>
            <atom:updated>2026-10-06T11:12:27.261Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR:</strong> On Wednesday, the company that sells email security to much of the Fortune 500 told its customers to go switch a feature off. By the next morning, the US cyber agency had added the bug to its catalog of flaws under active attack and given federal agencies until October 4 to deal with it. For most organizations running FortiMail, there is still nothing to install.</p><h3>What Happened?</h3><p>A critical flaw in FortiMail, the vendor’s email security gateway, is being exploited in the wild. It is tracked as CVE-2026–104286 and carries a CVSS score of 9.8, close to the ceiling.</p><p>The bug lives in the web management interface, specifically the component behind identity-based encryption. It combines a path traversal weakness with sloppy handling of null characters. An attacker with no account and no password can send a crafted HTTP or HTTPS request and write files anywhere on the underlying system. The vendor lists the impact as running unauthorized code or commands.</p><p>Four branches are affected: 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, and 7.2.0 through 7.2.9. The repaired builds for the first three are described as upcoming, which means they do not exist yet. Customers on 7.2 are told to move to the 7.4 branch or later. There is no virtual patch either.</p><p>The vendor’s product security team found the flaw internally. It was already being used in attacks when they found it. Nobody has said who is behind the campaign, when it started, or how many appliances were taken.</p><h3>The Impact</h3><p>The published indicators tell a sharper story than the severity score does.</p><p>On compromised appliances, attackers added four files and modified three more. One addition was an ld.so.preload entry, which quietly forces a planted library into running processes. The attackers also rewrote the web server configuration.</p><p>Then came the part that should worry mail administrators most. The attackers created an archive account from the command line and pointed it at a server they controlled, writing to a directory called /uploads. A mail gateway reads every message the organization sends and receives. Turning its own archive function into an outbound feed is a clean way to steal mail without deploying anything that looks like malware.</p><p>Two factors make this worse than a normal critical bug. The appliance is built to face the internet, so exposure is the default, not a misconfiguration. And because it was attacked before anyone knew the flaw existed, applying the workaround today says nothing about what happened last week.</p><p>CVE-2026–104286 · FG-IR-26–175</p><h3>FortiMail indicators of compromise</h3><p>Published by the vendor on October 1, 2026. Check every FortiMail appliance against this list before you change anything, because applying the workaround does not tell you whether someone already got in.</p><p>Files added or modified 7 artifacts</p><p>Network indicators 2 addresses</p><p>Also appears as the remote destination for the rogue mail archive account.</p><p>Listed in the advisory with no further context. Search firewall, proxy and NetFlow records.</p><p>Log entries to hunt 4 patterns</p><p>type=kevent subtype=config user=admin ui=cli msg=”Added ‘archive234’ to ‘archive account’ … remote-ip[79.141.169.187] remote-username[archive234] remote-directory[/uploads]”</p><p>A mail archive account pointed at attacker infrastructure. The clearest single sign of compromise.</p><p>type=event subtype=system pri=debug user=system ui=cron msg=”(root) CMD (/bin/sh -c ‘O=/migadmin …</p><p>A scheduled task running as root out of the migration admin path.</p><p>FortiMail::IBE::DecrypterMediaIn … Caught BufferException(2), BufferImpl.cpp:973, ‘Invalid Base64 Encoding at pos 0. Character=0x2a’</p><p>Hex 0x2a is an asterisk. These decode errors line up with the malformed requests that trigger the bug.</p><p>type=kevent subtype=admin action=logout status=success reason=unknown msg=”User admin logged out from (null).”</p><p>Admin session activity with a null source. Weak on its own, useful next to the others.</p><p>Source: vendor PSIRT advisory FG-IR-26–175, published October 1, 2026.</p><h3>How to Avoid This</h3><ul><li>Disable identity-based encryption with the three-line CLI command, or pull the management interface off the public internet and limit it to a trusted private network. Either one closes the door today.</li><li>Treat every appliance between 7.2.0 and 8.0.1 as vulnerable until the vendor says otherwise.</li><li>Hunt before you change anything. Preserve logs, configuration backups, and forensic images first, because a reboot or an upgrade can erase the evidence you need.</li><li>Check your archive accounts and remote destinations by hand. An account nobody remembers creating is the loudest signal in the whole advisory.</li><li>Then make the rule permanent. Management interfaces on security appliances don’t belong on the public internet, and that decision shouldn’t wait for the next advisory.</li></ul><p><em>Originally published at </em><a href="https://www.secure.com/news/fortimail-zero-day-exploited-no-patch"><em>https://www.secure.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb9387c33275" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your SIEM Isn’t Missing Alerts. It’s Missing the Path.]]></title>
            <link>https://medium.com/@securedotcom/your-siem-isnt-missing-alerts-it-s-missing-the-path-09be4b68e614?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/09be4b68e614</guid>
            <category><![CDATA[siem]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 11:37:54 GMT</pubDate>
            <atom:updated>2026-09-14T11:37:54.644Z</atom:updated>
            <content:encoded><![CDATA[<p>Every security team knows this feeling. You trace a real attack path from start to finish: initial access, lateral movement, privilege escalation. Somewhere in the middle, the SIEM goes quiet. Not because nothing happened. Because that one step produced a weak signal, a field that never got parsed, or a rule built for events that don’t look the way they do in your environment.</p><p>A recent thread on r/AskNetsec covered this exact problem. The advice in the comments was better than most vendor content on the topic, including what we might have written if we’d just shown up to pitch.</p><p><strong>What the thread got right</strong></p><p>Three points kept coming up, from different people, independently:</p><ol><li><strong>The real gaps are in telemetry, not rules.</strong> Missing log sources. Fields that don’t match across systems. Events that never reach the SIEM in a form a rule can read. No amount of alert tuning fixes a detection built on data that was never captured.</li><li><strong>Testing one alert at a time isn’t enough.</strong> A rule can pass on its own and still fail once it needs to connect to the event before it and after it. The fix is to test full attack paths, mapped to something like MITRE ATT&amp;CK, so you can see exactly where the chain breaks.</li><li><strong>This work never really ends.</strong> A SIEM isn’t like antivirus, set once and left alone. It needs constant tuning as your systems, your logs, and real attacker behavior keep changing. As more than one person put it: this is the job, not a project you finish.</li></ol><p>All three points are right. They’re also why so many teams stay stuck. Doing this properly takes real time: mapping out attack paths, tracing them through your actual logs, finding the exact step where visibility drops, then fixing the logging or rewriting the detection rule. And you have to keep doing it. For every path that matters, not just the one that caused your last incident.</p><p><strong>Where it breaks down at scale</strong></p><p>Nobody in that thread was wrong about the fix. Think like an attacker. Test the full chain. Close the gaps you find. Repeat. The hard part is “repeat.” Your attack surface changes every week. New services get connected. Log formats drift. A path that was fully covered in January can have a silent gap by September, and no one finds out until it’s too late.</p><p>That’s where manual attack-path testing struggles. Not because the method is wrong, but because it’s ongoing work competing with everything else on a security team’s plate.</p><p><strong>Where we come in</strong></p><p>This is the exact problem our Red Teammate is built to solve. It runs continuous recon and exploit validation, mapped to MITRE ATT&amp;CK, so you see your environment the way an attacker does. Not a one-time pentest report, but an ongoing view of what’s actually reachable and exploitable right now. Instead of checking one rule at a time, it links findings into ranked, exploitable attack paths. That’s the exact gap the r/AskNetsec thread described: the quiet step between initial access and privilege escalation. You find it before an incident forces you to.</p><p>Here’s the part that matters most: that evidence doesn’t just sit in a report. It feeds straight into our SOC Teammate, which prioritizes cases using the real business context of what’s exploitable, not just a CVSS score. The teammate that attacks teaches the teammate that defends. Every consequential action still needs your approval. The work moves to the teammate. The authority stays with your team.</p><p>We’re not saying this replaces good fundamentals. Clean telemetry, proper normalization, and constant tuning are still the foundation. No tool replaces having the right logs in the right format. What changes is the pace: instead of finding a gap during a tabletop exercise, or worse, during a real incident, you find it continuously, checked against your live environment, with the evidence already connected to what your team needs to act on.</p><p>If you’re doing the manual version of this today, walking attack paths by hand and patching gaps as you find them, you’re doing the right thing. The real question is whether you can keep doing it at the pace your environment actually changes.</p><p>Secure.com builds governed AI Teammates for security teams: Red, SOC, Cloud, AppSec, and GRC. They do real work inside the scope, permissions, and approvals you set. Learn more at secure.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09be4b68e614" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hackers Are Stealing Claude AI Login Sessions to Walk Straight Past Your 2FA]]></title>
            <link>https://medium.com/@securedotcom/hackers-are-stealing-claude-ai-login-sessions-to-walk-straight-past-your-2fa-8ae580977ba9?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ae580977ba9</guid>
            <category><![CDATA[anthropic-claude]]></category>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 07:46:54 GMT</pubDate>
            <atom:updated>2026-08-31T07:46:54.514Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR: </strong>Your password held. Your two-factor code held. And someone still got into your account. That is the unsettling reality behind a new wave of attacks hitting AI users right now. A major AI provider has started warning customers that criminals are lifting their saved login sessions off infected computers, then using those sessions to sign in as them. No password guessing. No 2FA prompt. The account just opens, because to the system, the attacker looks like a user who is already logged in.</p><h3>What Happened?</h3><p>The provider began signing affected users out and stripping saved payment cards from their accounts, then emailing them to explain why. The cause was infostealer malware sitting on the victim’s own machine. This kind of malware is built to stay quiet. It does not lock files or demand money like ransomware. It copies saved passwords, browser cookies, and active login tokens, then ships them to a remote server, in some cases in batches every few minutes.</p><p>One victim traced the infection back to a pirated game that carried a hidden stealer. It pulled their browser credentials, cookies, and session IDs. The malware families flagged in this campaign include Vidar, Lumma, StealC, RedLine, and Acreed on Windows, plus Atomic Stealer on a small number of Macs. Standard antivirus did not catch it.</p><h3>What’s the Impact?</h3><p>Here is the part that should worry every team, not just AI users. Two-factor authentication did not stop this. It could not. The attacker never faced a login screen. A stolen session token is proof that 2FA already passed, so the account never asks again. That is session hijacking, and it turns MFA into a speed bump the attacker simply drives around.</p><p>The reach goes well beyond one product. The same stealer that grabs an AI session also grabs email, cloud, and SSO tokens from the same browser. Research this year tied infostealers to billions of stolen credentials across millions of devices. One infected laptop can quietly expose a whole stack of corporate accounts. And the theft keeps working after the malware is gone, because the stolen tokens live off the device.</p><p>Indicators of Compromise</p><h3>Infostealers hijacking AI login sessions</h3><p>Behavioral and family-level indicators reported in the current campaign. No fabricated hashes or IP artifacts. Treat family names as time-sensitive.</p><h3>Malware families named in this campaign</h3><h3>Behavioral indicators to hunt for</h3><ul><li><strong>Usage that refills then drains</strong> while the real user is idle. The clearest account-side signal.</li><li><strong>Active sessions from unfamiliar IPs or geographies</strong> on AI and SaaS accounts.</li><li><strong>Logins with no matching password or 2FA event</strong>, a sign of replayed session cookies.</li><li><strong>Repeated outbound connections on a short timer</strong> from an endpoint, credentials sent in batches every few minutes.</li><li><strong>Browser cookie and saved-credential files accessed</strong> by an unexpected process.</li></ul><h3>Common delivery routes</h3><ul><li>Pirated games, cracks, keygens, and repacked installers.</li><li>Unofficial downloads and malicious apps posing as legitimate software or updates.</li><li>Malvertising and SEO-poisoned “free software” pages.</li></ul><p><strong>Response note:</strong> Removing the app does not undo the theft. Stolen cookies and tokens work off-device, so revoke and rotate. Wipe and rebuild the endpoint if a stealer ran, reset passwords from a clean device, and sign out every session to invalidate copied tokens.</p><h3>How to Avoid This</h3><ul><li>Treat any machine that ran a stealer as compromised. Back up clean data and rebuild it rather than trusting a quick removal, since many stealers plant restore files.</li><li>Reset passwords from a device you trust, never the infected one.</li><li>Sign out everywhere and revoke active sessions to kill the stolen tokens attackers are replaying.</li><li>Move high-value accounts to passkeys or hardware keys, which bind login to the device and blunt cookie replay.</li><li>Watch for the tell: usage or activity that spikes while you are idle. That is often a hijacked session at work.</li><li>Steer clear of pirated software, cracks, and unofficial downloads. That is the front door for most of these infections.</li></ul><p>Session Hijack · How It Works</p><h3>Why a stolen cookie walks past your 2FA</h3><p>Attackers are not cracking passwords. They copy the login session your browser already holds, then replay it. To the account, that stolen session looks like you, already signed in.</p><p>Exfiltration</p><p>Account Takeover</p><p><em>Originally published at </em><a href="https://www.secure.com/news/infostealers-hijack-ai-login-sessions"><em>https://www.secure.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ae580977ba9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A 9.8 Bug, No Workaround, and Only One Way Out]]></title>
            <link>https://medium.com/@securedotcom/a-9-8-bug-no-workaround-and-only-one-way-out-2b9dce8671a4?source=rss-1d50934ca651------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b9dce8671a4</guid>
            <dc:creator><![CDATA[Securedotcom]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 09:44:40 GMT</pubDate>
            <atom:updated>2026-08-10T09:44:40.343Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Happened?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DuP8YJkDV7y2UIPZR8WHwA.jpeg" /></figure><p>On August 5, the vendor released a hardening update for its IOS XE software. This is the operating system inside a large slice of business routers and switches.</p><p>Instead of listing dozens of separate bugs, the company grouped them by weakness type and gave each group one tracking ID. Seven groups in total.</p><p>The worst one covers command and code injection. That is the classic flaw where an attacker slips instructions into a device and gets it to run them. It carries a 9.8 severity score, about as high as it goes. A second critical group, scored 9.0, covers broken access control, meaning login and permission checks that can be dodged.</p><p>The rest cover memory bugs, math errors, bad input checks, and control flaws. Each one earned a high 8.6.</p><p>The part worth pausing on is how they were found. The vendor said the review used its normal testing plus frontier AI models. This is part of a new plan to run AI-assisted bug sweeps on a set schedule and ship grouped fixes twice a month.</p><p>So the same kind of AI that attackers use to speed up their work is now being pointed the other way, at finding flaws before the bad guys do.</p><h3>What’s the Impact?</h3><p>These devices sit at the center of business networks. Take over a router, and you can watch traffic, redirect it, or use the box as a door into everything behind it.</p><p>That is not a hypothetical fear for this product line. A couple of years back, a critical IOS XE bug got used to compromise tens of thousands of devices. The stakes are known.</p><p>This time there is no active attack yet, and that is the good part. But a published fix is also a map. Once patch details are public, skilled attackers study the changes to work out what the hole was. The clock starts the moment the advisory drops.</p><p>The flaws hit IOS XE running in autonomous or controller mode, no matter how the device is set up. There is no config tweak that closes the gap. You update or you stay exposed.</p><h3>How to Avoid This</h3><ul><li>Patch now. Not next quarter. Match your running version to the fixed release in the IOC sheet above and upgrade.</li><li>Find every affected box first. You cannot patch what you do not know you own, so run a fresh scan of your network gear before you start.</li><li>Rank by exposure. Anything facing the internet or sitting at a network chokepoint goes first.</li><li>Watch for odd device behavior while you roll out fixes. Strange logins, config changes you did not make, or new admin accounts are all worth a hard look.</li><li>Set a real patch clock for critical network gear, measured in days, not months.</li></ul><p><em>Originally published at </em><a href="https://www.secure.com/news/ai-finds-critical-flaws-cisco-ios-xe"><em>https://www.secure.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b9dce8671a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>