Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

Blog · 2-hour update · 2026-10-27

CVE-2026-105781 Adobe Campaign Classic (ACC: critical remote flaw, how to fix

By the PatchTheCVE security team · Updated 2026-10-27 · Data from NVD, CISA KEV, EPSS and vendor advisories

Most urgent: CVE-2026-105781: Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Comm
Critical severity (CVSS 10.0), remotely exploitable, no login needed. Recommended action: apply the vendor mitigation.

On 27 October 2026, 129 new CVEs were published that we track: 22 critical, 0 already exploited in the wild (CISA KEV) and 24 with a fix or vendor patch available. Each one is ranked by severity, exploitation signals and how easy it is to reach, so you can patch the right ones first.

Key takeaways

What happened in this 2-hour window: the most serious item is CVE-2026-105781 (critical, CVSS 10.0, priority 40/100). Recommended action: apply the vendor mitigation. 8 of the 8 top items can be attacked remotely without a login. Most affected: tanium (22), tp-link systems inc. (5), gnupg (1). 24 of 129 new CVEs already have a fix or vendor patch; for the other 105, follow the downgrade or mitigation steps until one ships.

Patch these first

CVE-2026-105781: Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Comm

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

CVE-2026-114595: In EPICS Base release 7.0.10 and prior, an integer overflow in network request processing can cause memory to

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

CVE-2026-103594: A stack-based buffer overflow vulnerability in Fireware OS's WireGuard configuration processing allows a remot

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

CVE-2026-108142: A vulnerability allowing an unauthenticated attacker to bypass authorization on the CDP Coordinator Service.

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

CVE-2026-108015: Private keys for eight eMudhra intermediate CA certificates have been compromised https://emudhra.we-have-a-p

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

CVE-2026-108014: Private keys for eight eMudhra intermediate CA certificates have been compromised https://emudhra.we-have-a-p

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

CVE-2026-93866: An integer overflow vulnerability in the WebSocket connection handling used by WatchGuard Fireware OS's Access

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

CVE-2026-93865: A missing authentication vulnerability in the Fireware OS FireCluster synchronization daemon allows a remote,

Why it ranks here: critical severity; remotely exploitable, no login, no user action.

References: NVD

Most affected vendors

How to act on this list

  1. Start with anything marked exploited or patch now.
  2. Check what you run: see how to check a version and patch it on Linux, Windows, pip and npm.
  3. Prefer the vendor or distro fix. If none exists, read when to downgrade and when to mitigate.
  4. Verify afterwards. Distros often fix a flaw without changing the upstream version, here is how to confirm.

FAQ

What is the most serious vulnerability published on 27 October 2026?

CVE-2026-105781 (Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Comm) ranks highest, with a priority score of 40/100. Recommended action: apply the vendor mitigation.

Are any of the new CVEs exploited in the wild?

None of the new CVEs were on the CISA Known Exploited Vulnerabilities list when this was written. Keep watching the list, it changes daily.

Should I downgrade if there is no fix yet?

Only when an older release is confirmed unaffected and the package is not a core system component. Downgrades can break dependent software, so test first and hold the package until a fix ships.

Sources

Share this briefing: LinkedIn · X · Reddit · WhatsApp · Email · RSS

Keep reading

← All posts

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.