Skip to main content
VulnerabilityPublished Updated

CVE-2026-104356: HaschekSolutions pictshare · PRNG

Affects HaschekSolutions pictshareSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 3.7.1 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.15.9
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.7.1
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade HaschekSolutions pictshare to 3.7.1.

Affected software

ProductAffectedFixed in
HaschekSolutionspictshareAffected
  • >=2.0.0 <3.7.1
Fixed in
  • 3.7.1
GitHubpictsharepkg:github/pictshareOther threatsAffected
  • >=2.0.0 <3.7.1
Fixed in
  • 3.7.1

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

AI-suggested

Upgrade PictShare to version 3.7.1 or later, where this vulnerability is fixed. No other mitigation is indicated or required according to the available data.

Description

PictShare versions prior to 3.7.1 use a weak pseudo-random number generator (PRNG) in the getRandomString() function to create delete_code authorization tokens. This vulnerability allows attackers to predict or infer the PRNG state and guess valid delete_code values, enabling unauthorized deletion of hosted files without needing to access the code from the info endpoint. The issue is fixed in version 3.7.1.

References

Community reviews

Loading reviews…