⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Low · CVSS 1.3

How to Fix CVE-2026-0228: Code Injection RCE in Cloud NGFW

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 1.3 - Low
Actively exploited?Not currently listed in CISA KEV
Affected11.2.0 < 11.2.8, 11.1.0 < 11.1.11, 10.2.0 < 10.2.17, 10.2.0 < 10.2.10-h28
Fixed inAll, 12.1.0
Type (CWE)CWE-295: Improper Certificate Validation

What is CVE-2026-0228?

CVE-2026-0228 is a code injection flaw in Cloud NGFW. Attacker-controlled input is evaluated as code by the application runtime, giving the attacker arbitrary execution inside the process. Vendor description: An improper certificate validation vulnerability in PAN-OS allows users to connect Terminal Server Agents on Windows to PAN-OS using expired certificates even if the PAN-OS configuration would not normally permit them to do so.

Why this CVE matters

Code injection against an application server is a direct path to remote code execution. The attacker executes inside the application runtime, which means database credentials, integration keys, and any secrets the process has loaded in memory are all exposed.

For deployments of Cloud NGFW that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

On PAN-OS, run show system info | match sw-version from the CLI, or read the Dashboard widget in the GUI.

How to fix CVE-2026-0228

  1. Read the vendor advisory in full: https://security.paloaltonetworks.com/CVE-2026-0228
  2. Upgrade Cloud NGFW to All, 12.1.0 or a later version listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
  5. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  6. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Upgrade PAN-OS to the patched release


# Target PAN-OS build All.
show system info | match sw-version

request system software download version All
request system software install version All
request restart system

# Post-reboot verification
show system info | match sw-version

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://security.paloaltonetworks.com/CVE-2026-0228
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2026-0228 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in Cloud NGFW, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-0228 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-0228?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my Cloud NGFW was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*