Skip to main content
← All vulnerabilities
CVE-2026-62860

Picsou vulnerable to login timing attack

Picsou (picsou-finance by Zoeille) versions before 1.0.8 have a login timing difference that can reveal which usernames exist. Fixed in 1.0.8.

Published
Last modified
published
Not listed in CISA KEV
Unclear
Fix
Fixed in 1.0.8
None on Exploit-DB, Metasploit or GitHub

Summary

Picsou, a self-hosted personal finance dashboard, is affected through its login endpoint, which lets an attacker determine whether a username exists by measuring response timing. The weakness does not expose or change account data on its own, but valid usernames discovered this way could support credential guessing attacks.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

Picsou is a self-hosted personal finance dashboard. In the affected login implementation, the `/api/auth/login` endpoint reveals whether a username exists through a timing discrepancy. In `backend/src/main/java/com/picsou/controller/AuthController.java`, `AuthController.login()` throws `BadCredentialsException` immediately for an unknown username, before `passwordEncoder.matches(...)`, whereas an existing username with an incorrect password incurs the `bcrypt` comparison cost. Both cases return the same generic `HTTP 401` response, but repeated latency measurements disclose valid usernames without credentials. Login rate limiting, a small user population, and deployments inaccessible from outside the local network limit practical exposure; the weakness does not itself read or modify account data, though enumerated usernames can assist credential stuffing or brute-force attacks. This issue is fixed in repository release 1.0.8.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Zoeille picsou-finance

    fixed in 1.0.8

References 3

GitHub · Cloeille/picsou-finance

FAQ

Questions about CVE-2026-62860

What does this mean?

The /api/auth/login endpoint takes a measurably different amount of time when a username exists with a wrong password than when the username does not exist. Someone without any credentials can use that difference to work out which usernames are valid on the instance.Source: github.com

Am I affected, and how do I check?

The listed affected range is picsou-finance versions before 1.0.8. To check an installation, look up the installed picsou-finance version and compare it with 1.0.8.Source: github.com

What should I do about it?

Upgrade picsou-finance to 1.0.8 or later, which is the listed fixed version.Source: github.com

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data