Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Go github.com/ory/kratos < 1.3.1-0.20260320110106-9d7085948039
Fixed in
1.3.1-0.20260320110106-9d7085948039· Vendor fix available
Issue
The ListCourierMessages Admin API in Ory Kratos is vulnerable to SQL injection due to flaws in its pagination implementation. Pagination tokens are encrypted using the secret configured in secrets.pagination. An attacker who knows this secret can craft their own tokens, including malicious tokens that lead to SQL injection. If this configuration value is not set, Kratos falls back to a default pagination encryption secret. Because this default value is publicly known, attackers can generate valid and malicious pagination tokens manually for installations where this secret is not set. Preconditions This issue can be exploited when the following conditions are met: - ListCourierMessages API is directly or indirectly accessible to the attacker - The attacker can pass a raw pagination token to the affected API - The configuration value secrets.pagination is not set or known to the attacker Impact An attacker can execute arbitrary SQL queries through forged pagination tokens.…
Recommended action: Upgrade to 1.3.1-0.20260320110106-9d7085948039 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Preconditions - The code login method is enabled with the passwordlessenabled flag set to true . - A 2FA method such as totp is enabled. - requiredaal of the whomai check or the settings flow is set to highestavailable. AAL stands for Authenticator Assurance Levels and can range from 0 (no factor) to 2 (two factors). - A user uses the code method as the only login method available. They do not have a password or any other first factor credential enabled. - The user has 2FA enabled. - The user’s availableaal is incorrectly stored in the database as aal1 or aal0 or NULL. - A user signs in using the code method, but does not complete the 2FA challenge. Example server configuration Below you will find an vulnerable example configuration. Keep in mind that, for the account to be vulnerable, the account must have no first factor except the code method enabled plus a second factor. Impact Given the preconditions, the highestavailable setting will incorrectly assume that the identity’s…
Recommended action: Upgrade to 1.3.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.