dbcve.org
Panorama Collaborative Operation \& ExecutionApplication · Codra

CVE-2026-4761

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
When a certificate and its private key are installed in the Windows machine certificate store using Network and Security tool, access rights to the private key are unnecessarily granted to the operator group. * Installations based on Panorama Suite 2025 (25.00.004) are vulnerable unless update PS-2500-00-0357 (or higher) is installed * Installations based on Panorama Suite 2025 Updated Dec. 25 (25.10.007) are not vulnerable Please refer to security bulletin BS-036, available on the Panorama CSIRT website: https://my.codra.net/en-gb/csirt.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

When certificates and private keys are installed in the Windows certificate store using the Network and Security tool in Panorama Suite 2025 (25.00.004), the tool incorrectly grants access rights to the private key to the Windows 'operator' group, exposing the private key to all operator-level users who should not have access. This is an improper access control vulnerability allowing potential privilege escalation and unauthorized access to sensitive cryptographic material.

MitigationApply vendor update PS-2500-00-0357 or higher, or upgrade to Panorama Suite 2025 Updated Dec. 25 (25.10.007) to remediate the incorrect certificate store permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Panorama Collaborative Operation \& ExecutionApplication
Affected:= 25.00.004
Panorama ComApplication
Affected:= 25.00.004
Panorama E2Application
Affected:= 25.00.004
Panorama H2Application
Affected:= 25.00.004

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Panorama Suite version
    Check the installed version of Codra Panorama Suite (Collaborative Operation & Execution, Com, E2, or H2) against version 25.00.004
    Affected if The installed version is exactly 25.00.004
  2. Identify certificates installed via Network and Security tool
    Use Windows certlm.msc (Certificate Manager for Local Computer) or certmgr.msc (Current User) to enumerate certificates installed in the Windows certificate store. Cross-reference installation dates with when the Network and Security tool in Panorama Suite was used.
    Affected if Certificates and private keys were installed using the Network and Security tool in the affected version
  3. Inspect private key permissions in Windows certificate store
    For each private key in the certificate store, right-click the certificate, select 'All Tasks' > 'Manage Private Keys', or use PowerShell command 'Get-ChildItem Cert:\LocalMachine\My | ForEach-Object { $_.PrivateKey }' to inspect ACLs. Check if the 'Users' group or 'Operators' group has been granted access.
    Affected if The Windows 'operator' group or equivalent operator-level users have access permissions to private keys in the certificate store
  4. Check for unauthorized operator access
    Using a test account that is a member of the Windows operator group (e.g., 'Backup Operators', 'Network Configuration Operators', or 'Power Users'), attempt to access or export private keys from the certificate store where Panorama certificates are stored.
    Affected if An operator-level user can access or export private keys that should be restricted to administrators only

If Panorama Suite version 25.00.004 is installed AND certificates were installed via its Network and Security tool AND the operator group has access to those private keys, the environment is affected by CVE-2026-4761.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor update PS-2500-00-0357 or higher, or upgrade to Panorama Suite 2025 Updated Dec. 25 (25.10.007) to remediate the incorrect certificate store permissions.

Recommended fix High confidence

Panorama Suite 2025 Updated Dec. 25 (25.10.007) or apply update PS-2500-00-0357

  1. Identify the current Panorama Suite version installed (25.00.004)
  2. Apply update PS-2500-00-0357 or higher to the Panorama installation
  3. Alternatively, upgrade to Panorama Suite 2025 Updated Dec. 25 (version 25.10.007) which is not vulnerable
  4. Verify the update was successfully applied by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Panorama Collaborative Operation \& Execution Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4761 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data