Digest · Thursday

Security digest: November 12, 2026

3 editorial briefs and 3 critical advisories.

All digests · RSS · Markdown

Take stock

  • Act now: Check Point Gaia: Exploited Root Escalation via DynamicCLI. Anyone running Check Point Force Firewalls, Management or Log Servers, Multi-Domain servers or Maestro Orchestrators on R81 through R82.20, and especially gateways with the Mobile Access portal, SSL Network Extender, SAML, Captive Portal, UserCheck or Zero Phishing enabled.
  • Patch this week: PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE. Anyone self-hosting PostgreSQL where roles other than trusted administrators can log in and create objects, such as multi-tenant platforms, shared development databases and tools that let users run SQL, plus anyone who runs pg_restore on archives they did not create.
  • Check exposure: wfx-loot. Any organization or maintainer with a 'docs: dependency audit notes' pull request, a wfx-docs branch or the listed commit messages in a repository since November 10, 2026, and anyone who ran npm install on an affected commit.
  • PyPI: 1 critical advisory (rucio). Check with pip-audit (or: pip show <package>).
  • RubyGems: 1 critical advisory (activestorage). Check with bundle audit check --update.
  • NuGet: 1 critical advisory (Aspire.Dashboard.Sdk.linux-x64, Aspire.Dashboard.Sdk.linux-arm64, Aspire.Dashboard.Sdk.linux-musl-x64, Aspire.Dashboard.Sdk.osx-x64, Aspire.Dashboard.Sdk.osx-arm64, Aspire.Dashboard.Sdk.win-x64, Aspire.Dashboard.Sdk.win-arm64). Check with dotnet list package --vulnerable --include-transitive.
  • None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.

Editorial briefs

Act now

· Vulnerability · CVE-2026-123039, CVE-2026-109618

Check Point Gaia: Exploited Root Escalation via DynamicCLI

On its own this is a local bug, but attackers are already chaining it with PHP2Shell on gateway web portals to get root, plant backdoors and in some cases wipe ESXi hosts, so Check Point Force Firewall owners should install the November Jumbo take now and hunt for compromise.

Must act: Anyone running Check Point Force Firewalls, Management or Log Servers, Multi-Domain servers or Maestro Orchestrators on R81 through R82.20, and especially gateways with the Mobile Access portal, SSL Network Extender, SAML, Captive Portal, UserCheck or Zero Phishing enabled.

Can relax: Check Point Spark Firewall and Smart-1 Cloud customers, whom Check Point lists as unaffected by this flaw, and organizations that do not run Check Point products.

  1. Install the fixed Jumbo Hotfix take (R82.20 Take 14, R82.10 Take 52, R82 Take 132, R81.20 Take 174) on every gateway, cluster member, management and log server.
  2. If you cannot patch today, stop the daemon with dbset process:dynamic_server followed by dbset :save, accepting that Dynamic CLI commands will fail.
  3. Confirm the PHP2Shell fix from sk1000302 is also in place on any gateway with Mobile Access, SSL Network Extender, SAML, Captive Portal, UserCheck or Zero Phishing; the same Jumbo takes cover it.

Read the brief →

Check exposure

· Supply-chain compromise

wfx-loot: Hijacked GitHub Accounts Run CI Secret Stealer

Most organizations were not touched, but the check takes minutes and a hit means every secret and cloud role your workflows can reach is compromised, with cloud backdoors that survive rotation.

Must act: Any organization or maintainer with a 'docs: dependency audit notes' pull request, a wfx-docs branch or the listed commit messages in a repository since November 10, 2026, and anyone who ran npm install on an affected commit.

Can relax: Teams whose organizations show none of the indicators after a search across all repositories and branches, and consumers of packages other than the two named below.

  1. Search every organization for the probe: gh search prs "docs: dependency audit notes" --owner <org> --created ">=2026-11-10".
  2. For any account that opened a probe PR, revoke sessions, personal access tokens, OAuth grants (including GitHub CLI) and SSH keys, then reset the password.
  3. For any repository where a payload commit landed, rotate every Actions secret and variable, registry token, cloud key and AI provider key its workflows could read.

Read the brief →

Patch this week

· Vulnerability · CVE-2026-6460, CVE-2026-116322

PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE

An attacker needs a database login first, and no attacks have been reported, but crash code is public, 32 of the fixes are rated 8.8, and any role that can create objects can reach code execution, so update every server and client this week.

Must act: Anyone self-hosting PostgreSQL where roles other than trusted administrators can log in and create objects, such as multi-tenant platforms, shared development databases and tools that let users run SQL, plus anyone who runs pg_restore on archives they did not create.

Can relax: Single-application databases reachable only by trusted roles can take the update in the normal weekly window, and managed-service users mainly need to confirm their provider has applied it.

  1. Find every server version with SELECT version(); and every client with pg_dump --version and pg_restore --version.
  2. Update servers to 18.7, 17.12, 16.16, 15.20 or 14.25 and restart; packages may restart the service, but Patroni or custom units need a manual restart.
  3. Update C-language extensions in the same change, because PostgreSQL says full protection requires rebuilding them.

Read the brief →

Known exploited (CISA KEV) 0

Added to CISA’s catalog on this day: confirmed exploitation in the wild. Due date = CISA’s deadline for US federal agencies.

None.

Critical advisories by ecosystem 3

GitHub-reviewed advisories rated critical, published this day (Pacific time).

NuGet 1

Check: dotnet list package --vulnerable --include-transitive

PyPI 1

Check: pip-audit (or: pip show <package>)

RubyGems 1

Check: bundle audit check --update