Skip to content

High 7.8In CISA KEVPatch available

CVE-2026-123039

The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authenticating connecting processes. An authenticated local user can send a command to the socket and have it executed as root.

How scary is it?

updated 21 Nov 2026
  • No

    Works without logging in1

    Needs a login: a basic user account (CVSS PR:L).

  • No

    Reachable over the network1

    Needs local access to the machine, such as a shell or a logged-in user (CVSS AV:L).

  • Yes

    Proof-of-concept code is public2

    2 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • Yes

    Attacks seen in the wild3

    CISA lists it as exploited in the wild.

  • Yes

    On CISA's exploited list (since 13 Nov 2026)3

    CISA deadline for US federal agencies: 16 Nov 2026.

Scare-o-meter

Drop everything

Attackers are already on it. Patch now.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.3 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 2 products in an affected versioncheckpoint Quantum Security Gateway / checkpoint Quantum Security Management

    checkpoint Quantum Security Gateway: R82.10 with Jumbo Hotfix Take 50 or below, R82.20 with Jumbo Hotfix Take 10 or below, R82 with Jumbo Hotfix Take 130 or below, R81.20 with Jumbo Hotfix Take 173 or below

    checkpoint Quantum Security Management: R82.10 with Jumbo Hotfix Take 50 or below, R82.20 with Jumbo Hotfix Take 10 or below, R82 with Jumbo Hotfix Take 130 or below, R81.20 with Jumbo Hotfix Take 173 or below

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker already has local access to the machine

    CVSS attack vector: Local (AV:L). Local access required, such as a shell or a logged-in user.

    Source 1

  3. The attacker has a user account

    CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…

    Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

    CISA's required action for this KEV entry, due 16 Nov 2026 for US federal agencies.

    Source 3

CVSS
7.8Highscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 13 Nov 2026CISA deadline for US federal agencies: 16 Nov 2026unvetted proof-of-concept code on github
EPSS
3.3%chance of exploitation in the next 30 daystop 12% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
12 Nov 2026analysed here 21 Nov 2026

Do first. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
local
Weaknesses
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
checkpoint Quantum Security GatewayR82.10 with Jumbo Hotfix Take 50 or belowR82.20 with Jumbo Hotfix Take 10 or belowR82 with Jumbo Hotfix Take 130 or belowR81.20 with Jumbo Hotfix Take 173 or belowVendor says fixed in: not stated
checkpoint Quantum Security ManagementR82.10 with Jumbo Hotfix Take 50 or belowR82.20 with Jumbo Hotfix Take 10 or belowR82 with Jumbo Hotfix Take 130 or belowR81.20 with Jumbo Hotfix Take 173 or belowVendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • checkpoint:gaia_os
  • checkpoint:multi-domain_security_management
  • checkpoint:quantum_security_management

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 13 Nov 2026.
CISA due date
16 Nov 2026, the remediation deadline for US federal agencies
CISA required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Public exploit code
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 13 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 12 Nov 2026Published
  2. 13 Nov 2026Added to CISA KEV (exploited in the wild)same day later
  3. 13 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
  4. 13 Nov 2026CISA SSVC assessment: exploitation activesame day later
  5. 14 Nov 2026CVE record last updated1 day later
  6. 16 Nov 2026CISA remediation due date (US federal agencies)2 days later
  7. 21 Nov 2026Analysed by vulneraibility.com5 days later

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorLocalLocal access required (shell, logged-in user).
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredLowThe attacker needs basic user privileges.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2026-123039 being exploited?

Yes. CVE-2026-123039 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-123039?

CVE-2026-123039 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-123039?

Yes. A fix has been recorded for CVE-2026-123039. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-123039 affect?

CVE-2026-123039 affects checkpoint:gaia_os, checkpoint:multi-domain_security_management, checkpoint:quantum_security_management. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

2 references in the CVE record, grouped by the tags the record gives them.

Other links (2)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.