Smp46 vulnerabilities
Published CVEs affecting Smp46 products: 4 record(s), with severity, exploitation and fixes.
CVE-2026-108163
Medium · 6.5
CWE-307 Oct 10, 2026
Pingvin Share X before 1.22.0 Ineffective Authentication Rate Limiting via Throttler TTL
Pingvin Share X before 1.22.0 contains an ineffective rate limiting vulnerability because throttler TTL values specified in seconds are interpreted as milliseconds. Unauthenticated attackers can send effectively unthrottled requests to /api/auth/signIn, /api/auth/signIn/totp and /api/auth/resetPassword to brute-force passwords and TOTP codes.
CVE-2026-108162
Medium · 6.5
CWE-348 Oct 10, 2026
Pingvin Share X before 1.22.0 Rate Limit Bypass via Spoofed X-Forwarded-For
Pingvin Share X before 1.22.0 contains a rate limit bypass vulnerability that allows unauthenticated remote attackers to evade per-IP throttling because backend/src/main.ts unconditionally trusts proxy headers. Attackers can rotate spoofed X-Forwarded-For values against /api/auth/signIn, /api/auth/signIn/totp, and /api/auth/resetPassword to brute-force passwords and TOTP codes and forge logged client IP addresses.
CVE-2026-108157
High · 8.1
CWE-287 Oct 9, 2026
Pingvin Share X 0.19.0 before 1.22.0 Account Takeover via OAuth Email Linking
Pingvin Share X from 0.19.0 before 1.22.0 contains an improper authentication vulnerability that allows remote unauthenticated attackers to take over accounts by abusing automatic OAuth email linking in OAuthService.signUp(). Attackers can register a victim's unverified email on an enabled OAuth/OIDC provider, exploiting the missing email_verified check in GenericOidcProvider, to sign in as the victim including administrators while bypassing TOTP.
CVE-2026-44196
Critical · 9.1
CWE-287 May 12, 2026
Pingvin Share X Authentication Bypass Skips TOTP Two-Factor Check (CVE-2026-44196)
Pingvin Share X is a secure and easy self-hosted file sharing platform. From 1.14.1 to 1.16.2, a critical authentication bypass vulnerability allows an attacker who has obtained a valid username and password to skip the second-factor authentication (TOTP) requirement entirely. Although, an attacker still needs the user's password to reach this stage. This vulnerability is fixed in 1.16.3.