VulnerabilityPublished 30 Oct 2026

CVE-2026-62860: Zoeille picsou-finance · Timing Side Channel

Affects Zoeille picsou-financeSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.0.8 when convenient.

Data as of 30 Oct 2026, 21:06 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	5.3

Patch: Available – fixed in 1.0.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade picsou-finance and cloeille/picsou-finance to 1.0.8.

Affected software

Product	Affected	Fixed in
Zoeillepicsou-finance	Affected <1.0.8	Fixed in 1.0.8
GitHubcloeille/picsou-finance`pkg:github/cloeille/picsou-finance`Other threats	Affected <1.0.8	Fixed in 1.0.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to picsou-finance version 1.0.8 or later, where this timing discrepancy vulnerability is fixed. No additional mitigation is required once the update is applied.

Description

Picsou-finance version prior to 1.0.8 contains a timing discrepancy vulnerability in its login endpoint that allows an attacker to determine valid usernames by measuring response times. The login implementation throws an exception immediately for unknown usernames but performs a bcrypt password comparison for existing usernames, causing observable timing differences. This vulnerability does not expose or modify account data directly but can facilitate username enumeration, aiding credential stuffing or brute-force attacks. The issue is fixed in version 1.0.8.

Impact

An attacker can enumerate valid usernames by measuring response time differences during login attempts. This information can be leveraged to perform targeted credential stuffing or brute-force attacks. The vulnerability does not allow reading or modifying account data directly. The overall impact is limited by existing rate limiting, small user population, and network access restrictions.

Summary

The vulnerability in picsou-finance's /api/auth/login endpoint arises from a timing discrepancy that reveals whether a username exists. Specifically, the AuthController.login() method throws a BadCredentialsException immediately for unknown usernames before performing the bcrypt password comparison, whereas for existing usernames with incorrect passwords, the bcrypt comparison incurs additional processing time. Although both cases return the same HTTP 401 response, attackers can measure latency differences to enumerate valid usernames. Mitigating factors include login rate limiting, a small user base, and restricted network access. The flaw is addressed in release 1.0.8.

CWE-208Observable Timing Discrepancy (opens in a new tab)
Base weakness
Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Cross-Domain Search Timing (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 20:52 UTC

WeaknessesCWE-208

Technical details

References

Community reviews

Related threats