Broken access control in Probo public e-signature API
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
Probo before 0.224.0 has a public Trust Center e-signature API that does not verify signature ownership. Any authenticated trust center visitor who knows another visitor's signature identifier can complete that visitor's NDA signature or add entries to its audit trail. The flaw is tracked under CWE-639, and exploiting it requires a high complexity attack.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
Description from the CNA
Probo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Prior to version 0.224.0, the public Trust Center GraphQL API exposes acceptElectronicSignature and recordSigningEvent, both gated only by @authentication(required: PRESENT) @sessionOnly — any self-provisioned trust center identity can call them. The underlying esign.Service.AcceptSignature and esign.Service.recordEvent build the tenant scope from the client-supplied signatureId GID (coredata.NewScopeFromObjectID(req.SignatureID)) and load the signature by that GID. At no point do they verify that the signature belongs to the caller or that the caller's email matches the signature's SignerEmail. As a result, any authenticated trust-center visitor who possesses another visitor's signature GID can: (1) complete that visitor's NDA signature — overwriting signer name/IP/UA with attacker data and setting status to Accepted, which triggers the sealing worker to generate a completion certificate; (2) inject arbitrary audit-trail events into any signature's log. Both attacks defeat the non-repudiation and integrity guarantees of the e-signature system. This issue has been patched in version 0.224.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Probo to version 0.224.0, which contains the fix.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
- Fix · CNA probo (getprobo) Fixed in 0.224.0
Timeline
- 2026-11-11 Threatist record created from CVE-2026-76078
- 2026-11-13 CISA SSVC decision points changed
References
Other 5
- https://github.com/getprobo/probo/security/advisories/GHSA-22xj-f767-ppw6
- https://github.com/getprobo/probo/pull/1475
- https://github.com/getprobo/probo/commit/eb9274f2cd7101f89c21c18f6d7a3570f95aff32
- https://github.com/getprobo/probo/commit/f20c3d73d20fcce1344ee1a44bfa6d7f8c35471f
- https://github.com/getprobo/probo/releases/tag/probod%2Fv0.224.0
More getprobo vulnerabilities
- TI-2026-89878 Vertical privilege escalation in Probo lets admins grant owner role CVSS 3.1HIGH 7.2
- TI-2026-89875 Cross-tenant risk read via unvalidated references in Probo CVSS 3.1MEDIUM 4.9
- TI-2026-89879 Probo public Trust Center API leaks hidden objects across tenants CVSS 3.1LOW 3.7
- TI-2026-36726 Probo has an open redirect bypass via path normalization CVSS 3.1MEDIUM 4.7
- TI-2026-89876 Application layer denial of service in Probo GraphQL endpoint CVSS 3.1MEDIUM 4.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences