# CVE-2026-16527: Pcp: pcp pmproxy: unauthenticated access to /store endpoint allows bypassing pmcd access rules

> Unauthenticated attackers can bypass access controls via the pmproxy /store endpoint to overwrite metrics and execute arbitrary code on Red Hat systems.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2026
- **Updated:** 1 Oct 2026
- **Also known as:** AZL-94382, DEBIAN-CVE-2026-16527, GHSA-cf63-g57m-mc5r, UBUNTU-CVE-2026-16527

## What is CVE-2026-16527?

CVE-2026-16527 is a high-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can bypass access controls by sending crafted requests to the PCP pmproxy /store endpoint. This allows the attacker to overwrite any PMDA metric, leading to arbitrary code execution and system takeover.

Weakness: CWE-284 (Improper Access Control), CWE-306 (Missing Authentication for Critical Functionality)

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


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

Apply the vendor's patch.

## Is CVE-2026-16527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16527 is a high-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16527 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-16527/ (Markdown: https://insights.sbomify.com/CVE-2026-16527/index.md)
```

## Sources

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

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