# CVE-2026-0228: PAN-OS: Improper Validation of Terminal Server Agent Certificate

> Attackers can bypass certificate validation to connect Terminal Server Agents using expired certificates, undermining security controls in PAN-OS.

- **Severity:** Low 1.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:N/SA:N/E:U/AU:N/R:U/V:D/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 11 Feb 2026
- **Also known as:** GHSA-j8fr-767f-7h52

## What is CVE-2026-0228?

CVE-2026-0228 is a low-severity vulnerability in Palo Alto Networks Cloud NGFW, published on 11 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-0228?


## How do I fix CVE-2026-0228?

No fix has been published for CVE-2026-0228 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0228 being exploited?

There is no known exploitation of CVE-2026-0228 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0228 and fix it if it is affected.

What it is: CVE-2026-0228 is a low-severity vulnerability in Palo Alto Networks Cloud NGFW, published on 11 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0228 in the wild and no public exploit code.

Affected product: Palo Alto Networks Cloud NGFW. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0228/ (Markdown: https://insights.sbomify.com/CVE-2026-0228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0228
- OSV: https://osv.dev/vulnerability/CVE-2026-0228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0228/
Summaries are generated and may contain mistakes; the official description above is the record.