CVE-2026-117472

URL prefix handling permits API key read-scope bypass in Psono Server

Published Oct 27, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
Psono Server CE && EE versions 4.0.33 through 7.2.3 compared the request path for the bulk-secret-read endpoint with a hard-coded unprefixed path. In deployments configured with URL_PREFIX, the comparison failed and the POST request was authorized using write scope instead of read scope. An authenticated remote attacker with an unusual read-disabled, write-enabled API key could therefore retrieve encrypted secret data and nonces through the prefixed bulk-secret-read endpoint despite lacking read permission. The default configuration without URL_PREFIX was not affected.

Analysis

AI-generated

Technical impact

The vulnerability stems from an incorrect comparison of request paths in the bulk-secret-read endpoint when a URL_PREFIX is configured. An authenticated attacker with an API key that has write permissions but no read permission can send a POST request to the prefixed endpoint and bypass the intended read-scope check, thereby retrieving encrypted secret data and nonces that should otherwise be protected. This results in a confidentiality breach of sensitive credentials without requiring higher privileges beyond token ownership.

Affected Systems

esaqa GmbH’s Psono Server, both Community Edition and Enterprise Edition, for versions 4.0.33 through 7.2.3. Deployments that do not configure a URL_PREFIX are not affected. The flaw is present in all builds prior to the v7.2.4 release where the bulk-secret-read endpoint is implemented.

Risk and Exploitability

The CVSS score of 4.3 indicates a moderate impact because the attacker requires a pre‑existing API key with write privilege. EPSS data is not available and the vulnerability is not listed in the CISA KEV catalog, so widespread exploitation has not been documented. Nevertheless, in environments where write-only API keys exist and the URL_PREFIX is enabled, remote attackers can realistically read protected secrets through the bulk‑secret‑read API.

Remediation

Vendor Solution

Upgrade to Psono Server 7.2.4 or later.


OpenCVE Recommended Actions

  • Upgrade to Psono Server version 7.2.4 or later to apply the patch that correctly validates request paths for the bulk‑secret‑read endpoint.
  • If an upgrade cannot be performed immediately, disable the URL_PREFIX configuration or ensure that no services rely on it, restoring the default path comparison behaviour.
  • Review all API keys in use; revoke or recreate any keys that grant write access without read access, and enforce that keys used for secret reading include the necessary read scope.

Generated by OpenCVE AI on October 27, 2026 at 08:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Esaqa
Esaqa psono
Vendors & Products Esaqa
Esaqa psono
Type Values Removed Values Added
Description Psono Server CE && EE versions 4.0.33 through 7.2.3 compared the request path for the bulk-secret-read endpoint with a hard-coded unprefixed path. In deployments configured with URL_PREFIX, the comparison failed and the POST request was authorized using write scope instead of read scope. An authenticated remote attacker with an unusual read-disabled, write-enabled API key could therefore retrieve encrypted secret data and nonces through the prefixed bulk-secret-read endpoint despite lacking read permission. The default configuration without URL_PREFIX was not affected.
Title URL prefix handling permits API key read-scope bypass in Psono Server
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
esaqa
Published
Updated
Nov 4, 2026, 3:01 PM
Reserved
Oct 27, 2026, 5:33 AM
Status
Deferred
Published
Oct 27, 2026, 6:17 AM
Modified
Nov 4, 2026, 3:17 PM