Public vulnerability disclosure

CVE-2026-128970

Missing membership acceptance check permits group share-right deletion by invitees in Psono Server

publishedCWE-863

Psono Server Community Edition versions 1.12.6 through 7.5.0 and Psono Server Enterprise Edition before 7.5.1 do not require accepted group membership when authorizing deletion of group share-rights. The DELETE /share/right/ endpoint checks for a membership matching the target group, the authenticated user, and share_admin=True, but omits accepted=True. An authenticated remote attacker who has been invited to a group with share-admin privileges, and who knows a group share-right UUID, can therefore delete that group's share-right record without accepting the invitation or after declining it. Pending invitations have accepted=None, while declined invitations retain accepted=False and the share_admin flag. Deletion revokes the group's access to the affected share and its contained secrets for all accepted group members, without deleting the underlying data or disclosing secret contents. The issue was fixed in version 7.5.1 of both editions, released on 2026-10-13.

Technical severity5.4 mediumCVSS 3.1 · CNA: esaqa
Published2026-11-13Source updated 2026-11-13
Collected2026-11-132 attributed sources

Fixes and workarounds

Fix

Upgrade Psono Server Community Edition and Psono Server Enterprise Edition to version 7.5.1 or later. Version 7.5.1 was released for both editions on 2026-10-13. The patch adds accepted=True to the User_Group_Membership authorization query in DeleteShareRightSerializer.validate, making group share-right deletion require both accepted membership and share_admin=True, matching the group authorization check in the create path.

Source: CNA: esaqa

Workaround

Until the patch is deployed, use authorized group administration to remove pending and declined group memberships carrying share-admin privileges, or clear their share_admin flag. Avoid granting share-admin privileges to unaccepted invitees on affected versions.

Source: CNA: esaqa

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: esaqa

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Psono
esaqa GmbH
≥ 1.12.6; < 7.5.1 (affected, semver)
Other versions: unaffected
CNA: esaqa
Psono
esaqa GmbH
≥ 0; < 7.5.1 (affected, semver)
Other versions: unaffected
CNA: esaqa

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 5.4
medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LCNA: esaqa
3.1 / 5.4
medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LNVD: fdf66990-8419-4c8c-8848-ec15d75773b4

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide