Evidence comparison
Palo Alto Networks and Check Point: what the public record shows about each
Both products turn up on network security shortlists, so this page puts their two evidence records next to each other: 116 items on Palo Alto Networks and 137 on Check Point, each one linked to the source it came from. It does not name a winner, and the section below explains why the numbers cannot be subtracted from one another.
Read the counts correctly
More advisories does not mean less secure. A vulnerability register records what researchers found and what the vendor disclosed. A product deployed in thousands of organisations with a mature disclosure process accumulates far more entries than a product nobody audits. A low count can mean a small install base, a young product or a vendor that publishes little, and a high count often marks the opposite.
The two counts are not measured with equal precision. An advisory is only listed against a vendor when the register ties it to one of its products by name, and vendors differ enormously in how consistently their products are named. Here that gap is 1 unattributable entries for Palo Alto Networks against 104 for Check Point, which moves the advisory row far more than the products do. Both numbers are in the table so the difference is visible rather than hidden.
Treat this page as two records shown together, never as one score minus another.
The two records side by side
| Measure | Palo Alto Networks | Check Point |
|---|---|---|
| Evidence items in the recordSize of the record, not a quality signal. | 116 | 137 |
| Kinds of source | 5 | 5 |
| Advisories attributed to the vendor's productsCounts scrutiny and deployment breadth. See the caution above. | 98 | 12 |
| Register entries that could not be attributedEntries naming the vendor that could not be tied to one of its products, so they are excluded from the row above. Read the two rows together: where this number is high, the registers describe that vendor's products less consistently, and the advisory count above says more about naming than about the product. | 1 | 104 |
| Of those, in the CISA known-exploited catalogueExploitation observed in the wild. The one count worth reading closely. | 14 | 1 |
| Share from government registers | 87% | 85% |
| Share the vendor cannot edit | 100% | 100% |
| Public practitioner threadsReflects community size as much as product behaviour. | 13 | 1 |
| Most recent entry | Jul 17, 2026 | Jul 17, 2026 |
| Sources last re-queried | Jul 17, 2026 | Jul 17, 2026 |
Where each record comes from
The registers and platforms behind each column, with the body that operates each one. A record resting on government registers carries different weight from one resting on the vendor's own documentation, which is why this is shown per vendor rather than merged.
Palo Alto Networks
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| European Vulnerability Database | ENISA, European Union | Authoritative | 63 | Jul 09, 2026 |
| CERT-Bund security advisories | BSI, Federal Republic of Germany | Authoritative | 24 | Jul 10, 2026 |
| Known Exploited Vulnerabilities catalogue | CISA, United States | Authoritative | 14 | May 29, 2026 |
| Engineering discussions | Hacker News, public threads | Independent | 13 | Jul 03, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 2 | Jul 17, 2026 |
Check Point
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| European Vulnerability Database | ENISA, European Union | Authoritative | 102 | Jul 17, 2026 |
| CERT-Bund security advisories | BSI, Federal Republic of Germany | Authoritative | 10 | Jun 12, 2026 |
| Known Exploited Vulnerabilities catalogue | CISA, United States | Authoritative | 4 | Aug 25, 2025 |
| Engineering discussions | Hacker News, public threads | Independent | 16 | Jul 09, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 5 | Jul 17, 2026 |
Documented vulnerabilities
Only entries tied to a product of the named vendor by a structural signal are listed: an advisory reference on the vendor's own domain, the vendor as the assigning authority, or the affected product list naming it. Entries that merely mention a vendor in passing are excluded from both columns.
Palo Alto Networks
- CVE-2026-0257criticalCVSS 7.8Known exploitedMay 29, 2026
Palo Alto Networks PAN-OS Authentication Bypass Vulnerability
- CVE-2026-0300criticalCVSS 9.3Known exploitedMay 06, 2026
Palo Alto Networks PAN-OS Out-of-bounds Write Vulnerability
- CVE-2025-0111criticalKnown exploitedFeb 20, 2025
Palo Alto Networks PAN-OS File Read Vulnerability
- CVE-2025-0108criticalKnown exploitedFeb 18, 2025
Palo Alto Networks PAN-OS Authentication Bypass Vulnerability
- CVE-2024-3393criticalKnown exploitedDec 30, 2024
Palo Alto Networks PAN-OS Malicious DNS Packet Vulnerability
- CVE-2024-9474criticalKnown exploitedNov 18, 2024
Palo Alto Networks PAN-OS Management Interface OS Command Injection Vulnerability
Check Point
- CVE-2024-24919criticalKnown exploitedMay 30, 2024
Check Point Quantum Security Gateways Information Disclosure Vulnerability
- WID-SEC-2026-1818highCVSS 9.1Jun 12, 2026
Affected products: Check Point Security Gateway, Check Point Remote Access VPN, Check Point Mobile Access, Check Point Spark Firewall
- WID-SEC-2026-1746mediumCVSS 5.3Jun 01, 2026
Affected products: Check Point Security Gateway
- WID-SEC-2026-1726highCVSS 8.1May 29, 2026
Affected products: Check Point Security Gateway
- CVE-2026-48136mediumCVSS 4.1May 26, 2026
When Compliance is enabled on Check Point Multi-Domain Management, an authenticated administrator with read-write access to one Management Domain (CMA) can modify stored metadata associated…
- WID-SEC-2024-1743mediumCVSS 7.8Dec 02, 2024
Affected products: Check Point Zone Alarm
What practitioners report
Public threads naming each product in their own title. Not curated for sentiment, and not counted as a verdict: a loud thread is one team's experience, not a measurement.
Palo Alto Networks
- Hacker NewsJul 03, 2026Independent
Startup sues Palo Alto Networks' Koi Security due to AI-hallucinated report
- Hacker NewsNov 20, 2025Independent
Palo Alto Networks to buy Chronosphere for $3.35B
- Hacker NewsNov 19, 2025Independent
Palo Alto Networks to Acquire Chronosphere
- Hacker NewsOct 12, 2025Independent
Cisco, Fortinet, Palo Alto Networks Devices Targeted in Coordinated Campaign
- Hacker NewsJul 30, 2025Independent
Palo Alto Networks agrees to buy CyberArk for $25B
Check Point
- Hacker NewsJun 10, 2024Independent
Free CVE-2024-24919 Scanner – Check Point VPN Vulnerability
What neither record can tell you
The two lists below are the honest holes in each record. Everything a choice between these two actually turns on sits outside both of them.
Palo Alto Networks
- A further 1 register entries mention Palo Alto Networks without naming a product of Palo Alto Networks as affected. They are excluded rather than counted as vulnerabilities.
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Check Point
- A further 104 register entries mention Check Point without naming a product of Check Point as affected. They are excluded rather than counted as vulnerabilities.
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Whether Palo Alto Networks is the right choice is not on this page
A record of what is true about a vendor is one half of a decision. The other half is your context: which criteria matter, how heavily each one weighs, what is a hard no, and who has to sign the result off. No public page can know that, and any page that claims to rank vendors for you is guessing at it.
Typical criteria for this category
Needs your case- Detection Accuracy (MITRE ATT&CK coverage)weight
- MDR / Managed Detection & Responseweight
- Deployment Complexityweight
- Automated Response / Remediationweight
- SIEM Integrationweight
Criteria shown as examples for network security. Weighting and fit are properties of your decision, not of the vendor, so they are not published here.
What DecisionOS adds on top of this record
- The vendor scored against your criteria with your weighting, not against a generic ranking
- A dealbreaker check against your hard constraints: data residency, contract terms, existing stack
- A side-by-side view of the alternatives on your shortlist, built from this same evidence pool
- This evidence mapped onto your compliance scope: NIS2, DORA, ISO 27001, SOC 2
- A decision memo your board can read, with the trade-offs and the reasoning on the record
Questions this page answers
Which is better, Palo Alto Networks or Check Point?
This page does not answer that, and no public page can. Better exists only relative to a decision: which criteria matter, how heavily each weighs, what counts as a dealbreaker and which systems the product has to live next to. What this page gives you is the evidence on both, 116 items on Palo Alto Networks and 137 on Check Point, each with its source, so the judgement rests on the record rather than on marketing.
Does Palo Alto Networks or Check Point have more vulnerabilities?
Palo Alto Networks currently has 98 attributed advisories in this record and Check Point has 12. That comparison is easy to misread. A vulnerability register records what researchers found and what the vendor disclosed, so a widely deployed product with an active disclosure process accumulates more entries than one nobody audits. A low count can equally mean a small install base or a vendor that publishes little. The two figures are also not measured with equal precision: an advisory only counts here when a register ties it to a named product, and 1 entries naming Palo Alto Networks and 104 naming Check Point could not be tied to one. The count worth reading closely is how many entries appear in the CISA catalogue of known exploited vulnerabilities, which is 14 for Palo Alto Networks and 1 for Check Point.
How independent is the evidence on Palo Alto Networks and Check Point?
100 percent of the Palo Alto Networks record and 100 percent of the Check Point record come from sources the vendor does not control: government vulnerability registers, public practitioner threads and a fixed list of recognised analysts and technology press. Material either vendor publishes about itself stays in the record and is labelled as a claim.
What does this comparison of Palo Alto Networks and Check Point leave out?
Pricing, contract terms, notice periods, support commitments and the current scope of any certificate. None of those appear in a public register; they come from the vendor and belong in a negotiation record. Fit with your existing stack and your compliance scope is also absent, because it is a property of your organisation rather than of a network security product.
Why does nexalign publish this instead of ranking Palo Alto Networks and Check Point?
Because a ranking would have to invent the buyer. Every quadrant and score sheet silently assumes a weighting that belongs to someone else's decision. nexalign publishes the record and keeps the weighting where it belongs, in DecisionOS, where it is set by the people who have to defend the outcome.
The full records
Palo Alto Networks: the full evidence record
116 items from 5 kinds of source
Check Point: the full evidence record
137 items from 5 kinds of source
Two records do not make a decision
Choosing between Palo Alto Networks and Check Point depends on which criteria matter to you, how heavily each one weighs, what your hard constraints are and who has to sign the result off. DecisionOS takes this same evidence pool, scores it against the criteria of your actual decision and produces a memo that holds up in front of a board and an auditor.