Daily Briefing   Edition date: October 28, 2026 · Latest source timestamp incorporated: CISA Known Exploited Vulnerabilities catalog, release of Oct 27, 2026, 3:00 p.m. ET.

SMB Cybersecurity Intelligence Briefing — October 28, 2026

Good morning! Welcome to October 28, 2026’s SMB Cybersecurity Intelligence Briefing.

Today we’re covering Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type Vulnerability (CVE-2026-48356), new vulnerabilities actively being exploited, and the actions you should take today to reduce ransomware, fraud, and downtime risk. Let’s get to it.

Assumed environment today: Profile A (Microsoft 365 + Windows endpoints).

Today’s decision summary

1. Top story of the day

Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type Vulnerability (CVE-2026-48356)

• What happened: On Oct 27, 2026 CISA added CVE-2026-48356 to its Known Exploited Vulnerabilities catalog, confirming active exploitation.
• Why it matters: Adobe Commerce and Magento contain an unrestricted upload of file with dangerous type vulnerability that could result in arbitrary code execution in the context of the current user, potentially gaining elevated access or control over the victim's account or session. Data exposure and downtime on that system are the risk. CISA lists ransomware use as Unknown.
• Threat type: Exploited Vulnerability
• Who is targeted: Organizations running Adobe Commerce and Magento (common desktop software). Industry and region: Not reported.
• Attack path: Initial access: network access, with no privileges required (from the NVD vector). Impact as CISA describes; further detail Not reported.

Action timeline

• Do in 4 hours: Check whether you run Adobe Commerce and Magento and note its version. If its management page faces the internet, limit it to a VPN or fixed addresses.
• Do in 24 hours: Apply the vendor’s mitigations or updates, or stop using the product if none are available (CISA required action), per the vendor notice below, then run the compromise check.
• Do in 7 days: List every internet-facing system you run and who updates it.

Assume compromise: patching locks out new attackers; it does not evict one already inside. If this system was internet-reachable at any time since exploitation began (start date not reported), run a compromise assessment, not patching alone. Look for new administrator or local accounts, unfamiliar sign-ins, unexpected outbound connections, unplanned service restarts and configuration changes you did not make. Keep the logs before rebuilding. IOCs: not reported by authoritative sources.

• Verification: In the product’s admin page, compare the installed version with the fixed version in the vendor notice (not reproduced here), then review the account list and recent sign-ins.
• Fallback if you can’t patch today: remove the management page from the public internet (VPN or address allow-list at your firewall) and watch its logs daily.
• If you have no IT staff: Ask whoever manages it: “Do we run Adobe Commerce and Magento, what version, and when was it updated?” If nobody knows, have them unplug it from the internet.
• Impact score: 3 of 5: exploited, but the NVD vector shows local access or limited impact, which narrows the blast radius.
• If you use an MSP: “Send me today the installed version of Adobe Commerce and Magento on every system you manage for us and its last update date, or confirm in writing we do not run it.”

Benchmark only: CISA’s federal due date is Nov 10, 2026; it does not bind your business.

Sources: CISA Known Exploited Vulnerabilities catalog, entry added Oct 27, 2026; NVD record for CVE-2026-48356, published Jul 14, 2026; Vendor or agency notice on adobe.com (publication date not reported).

2. Active threat & vulnerability updates

Google Brotli: CVE-2026-111497

• Status: Exploited per CISA, added Oct 27, 2026. CISA lists ransomware use as Unknown.
• Affected systems: Google Brotli; versions Not reported by CISA.
• Impact: Google Brotli contains an unchecked return value vulnerability that allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream.
• CVSS: CVE-2026-111497 v4.0 base 9.2 (Critical).
• Business risk: Medium (7d). Federal due date Nov 10, 2026 (benchmark only).
• Mitigation: vendor mitigations or updates; stop using the product if none exist (CISA required action).
• How to check exposure: find it in your asset list and read the installed version.

Sources: CISA Known Exploited Vulnerabilities catalog, entry added Oct 27, 2026; NVD record for CVE-2026-111497, published Oct 22, 2026.

CVSS scores are as published in each NVD record; where NVD has not scored a CVE itself, the score shown was supplied by the CVE’s assigning authority.

Status updates

• CVE-2026-109619 (PHP Group PHP) led the previous edition; its status has not changed.

Earlier on the list Durable (not new)

Older than 72 hours, shown for context:

• CVE-2026-109619 (PHP Group PHP), added Oct 26, 2026. PHP contains a stale internal request-state vulnerability that allows for unauthenticated remote code execution. CISA lists ransomware use as Unknown.
• CVE-2026-109618 (PHP Group PHP), added Oct 26, 2026. PHP contains an out-of-memory corruption vulnerability that allows for unauthenticated remote code execution. CISA lists ransomware use as Unknown.
• CVE-2026-114625 (Arista VeloCloud Orchestrator), added Oct 23, 2026. Arista VeloCloud Orchestrator on-prem contains a SQL injection vulnerability that may allow a remote attacker to access privileged internal functionality and impact the VCO host. CISA lists ransomware use as Unknown.
• CVE-2026-110447 (Collabora Online – Built-in CODE Server), added Oct 23, 2026. Collabora Online – Built-in CODE Server when used within the NextCloud platform contains an OS command injection vulnerability that allows for remote code execution when the CODE server isn't running. CISA lists ransomware use as Unknown.

Exploited-vulnerability news can distract from a cheaper attack: a convincing email. These checks close a path that needs no malware at all.

Sources: CISA Known Exploited Vulnerabilities catalog.

3. Security protocols & hardening

Exposure triage for an exploited internet-facing product

• Risk reduced: Intrusion through a flaw attackers are already using.
• Minimal steps:

1. Find every instance of the affected product, including old ones nobody owns.
2. Take its management interface off the public internet before you update it.
3. Apply the vendor’s fix, then run the compromise assessment above.
4. Rotate any credentials or keys the product stored.

• Verification: The installed version matches the vendor notice, the management page is unreachable from outside, and the account and configuration review found nothing unexpected.
• Common failure mode: Teams update the product and stop, leaving an intruder who got in before the update, and leave the old management page open.
• Cost: Low. Time to implement: 2 to 4 hours.

4. Tools & technology

Built-in controls first

• Your firewall or router’s published-services list. Minimum configuration: Open the port-forwarding or published-services page and remove entries nobody can name an owner for. Verification: From a phone on mobile data, not your office network, the removed addresses no longer answer.
• The affected product’s own audit log (or Event Viewer on a Windows host). Minimum configuration: Filter for account creation, failed sign-ins and service restarts since you installed it. Verification: You can explain every entry as expected, or you have escalated it.

5. Operational metrics snapshot

CISA’s Known Exploited Vulnerabilities catalog (release of Oct 27, 2026, 3:00 p.m. ET) lists 1,760 entries. In the 7 days to Oct 28, 2026, 6 were added, and 0 of those are marked as used in ransomware campaigns.

Sources: CISA Known Exploited Vulnerabilities catalog, release of Oct 27, 2026, 3:00 p.m. ET.

Closing

Tomorrow’s watch list:

• Any change to CISA’s ransomware flag or the vendor notice for CVE-2026-48356
• FBI IC3 or Canadian Centre for Cyber Security fraud alerts
• CISA additions for email products

Question of the day: Could one email change where we send money, and who would catch it?

Daily security win (10 minutes or less): Phone one supplier you pay regularly and confirm their bank details on file. Risk reduced: Redirected payments. How to verify: The details on the call match your records, and you noted the date.

This weekday’s theme: Wednesday is email and payments day, when invoices and payroll changes are in motion. Fraud succeeds at the handoffs between people, so the check is about the process as much as the mail settings.

Go deeper

• Patching known exploited vulnerabilities
• Internet-facing exposure
• MSP security expectations
• Payment-change verification

This briefing provides general information for operational risk reduction and is not legal, insurance, or incident-response advice. Verify all actions against your own environment and current vendor advisories before applying them. Vulnerability status and patch guidance change rapidly; confirm against the linked sources before acting.