CVE-2026-117470 json
WebAuthn assertion replay permits second-factor bypass in Psono Server
published 13d ago modified 5d ago also EUVD-2026-110604
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Psono Server CE & EE versions 3.1.0 through 7.2.3 did not consume a stored WebAuthn challenge after assertion verification. An unauthenticated remote attacker who possessed the user's password and one captured valid WebAuthn assertion could replay that assertion with separate login tokens while the stored challenge remained unchanged, bypassing the WebAuthn second factor. The attack required capture of a valid assertion and did not itself disclose plaintext secrets.
Patch / fix
- esaqa GmbH Psono 7.2.4
Is CVE-2026-117470 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5d ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N |
Affected products
- esaqa GmbH Psono
Classification
- Weakness
-
- CWE-294 Authentication Bypass by Capture-replay
References
-
gitlab.com
/esaqa/psono/psono-server/-/commit/9c9a7f1701535df63370340dcc80210737dc495d
patch
-
gitlab.com
/esaqa/esaqa/security-advisories/-/blob/master/advisories/CVE-2026-117470.md
vendor-advisory
-
gitlab.com
/esaqa/psono/psono-server/-/blob/v7.2.3/psono/restapi/serializers/webauthn_verify.py
technical-description
-
gitlab.com
/esaqa/psono/psono-server/-/releases/v7.2.4
release-notes
-
gitlab.com
/esaqa/psono/psono-server
product
Sources
- CVE List CVE-2026-117470
- NVD CVE-2026-117470
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.