CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.224.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects probod up to and including 0.224.0; the advisory reports it on v0.222.2 in default configuration.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
Who should check
Teams self-hosting Probo up to 0.224.0 that let organization ADMIN users manage memberships or create users.
Read the source excerpt
“Attacker holds the organization ADMIN role (or any principal with”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects probod up to and including 0.224.0; the advisory reports it on v0.222.2 in default configuration.Upgrade to a fixed version: 0.224.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- getprobo probo
fixed in 0.224.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-76079
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2026-76079?
probo: before 0.224.0.Source: cve.now feed data
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: github.com
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: github.com