esaqa GmbH vulnerabilities
Every vulnerability this feed holds for esaqa GmbH, merged from five public registers and ordered by what warrants attention first — exploited in the wild, then CVSS, then recency.
5 vulnerabilities tracked.
- 6.5 Psono Server CE & EE versions 3.1.0 through 7.2.3 did not consume a stored WebAuthn challenge after assertion verification.
- 6.5 Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code.
- 5.4 Psono Server CE && EE versions 0.1.0 through 7.2.3 accepted a user-controlled host when configuring a personal Duo device and passed it to…
- 5.4 Psono Server (CE & EE) versions 1.0.0 through 7.2.3 did not enforce the direction of file-transfer credentials on file-repository…
- 4.3 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…
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that esaqa GmbH is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other vendors tracked here
Google Microsoft Apple Red Hat zephyrproject Apache Software Foundation n/a Hewlett Packard Enterprise (HPE) MediaTek, Inc. Linux Eclipse Foundation Unknown FreeRDP Dell Tanium Oracle Corporation MONGODB Gitea WAVLINK vercel vim Hitachi jpadilla WSO2