CODRA
Panorama Suite
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-4761 | 25 Mar 2026 | Panorama Suite 2025 < update PS-2500-00-0357 | Panorama Suite 2025 Updated Dec. 25 | Update reference ↗ |
| CVE-2026-4760 | 25 Mar 2026 | Panorama Suite 2022-SP1 < update PS-2210-02-4079; Panorama Suite 2023 < update PS-2300-03-3078 AND PS-2300-04-3078 AND PS-2300-82-3078; Panorama Suite 2025 < update PS-2500-02-1078 AND PS-2500-04-1078; Panorama Suite 2025 Updated Dec. 25 < update PS-2510-02-1077 AND PS-2510-04-1077 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.