CVE-2026-104356
validatedZero produced an exploit or a check.GHSA-6654-r2c2-m62r ↗EUVD-2026-91072 ↗
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+11h41mkevAttacks confirmed in the real world.
HaschekSolutions pictshare >= 2.0.0, < 3.7.1
fixed in 3.7.1
CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
ETK-2026-284, permanent identifier
+57mTTV
15mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable description
PictShare versions before 3.7.1 generate file-deletion authorization tokens with a non-cryptographic random number generator. An attacker who can predict or infer its state may guess valid tokens and delete hosted files.
mitigation
Upgrade PictShare to version 3.7.1 or later.
fixed in 3.7.1
check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 21:21Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+11h41m
Δ to kevAttacks confirmed in the real world.
–
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-01 21:21Zcve_org: trigger signal, started the run
- 2026-10-02 19:36Zwvllxe/CVE-2026-104356-pictshare-weak-delete-code
this entry in the feed
GET /api/v1/feed/CVE-2026-104356
{ "etk_id": "ETK-2026-284", "cve_id": "CVE-2026-104356", "display_id": "CVE-2026-104356", "ghsa_id": "GHSA-6654-r2c2-m62r", "euvd_id": "EUVD-2026-91072", "status": "published", "anchor_state": "anchored", "title": "Predictable deletion tokens in PictShare", "summary": "PictShare versions before 3.7.1 generate file-deletion authorization tokens with a non-cryptographic random number generator. An attacker who can predict or infer its state may guess valid tokens and delete hosted files.", "mitigation": "Upgrade PictShare to version 3.7.1 or later.", "vendor": "HaschekSolutions", "product": "pictshare", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 2.0.0, < 3.7.1" ], "ecosystem": null, "fixed_versions": [ "3.7.1" ], "package_name": "pictshare", "purl": null } ], "cwes": [ 338 ], "cvss_score": 8.2, "cvss_src": "cna_vendor", "cvss_vector": "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", "epss_score": 0.0031, "epss_percentile": 0.2234, "epss_asof": "2026-10-20", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 14.6972294, "t0_at": "2026-10-01T21:21:45.992000+00:00", "signals": { "check": { "at": "2026-10-01T22:18:57.869430+00:00", "days": 0.03972080358796296, "is_lower_bound": false, "measured_at": "2026-10-01T21:21:45.992000+00:00", "url": null }, "public_poc": { "at": "2026-10-02T09:02:17+00:00", "days": 0.48647, "is_lower_bound": false, "measured_at": "2026-10-01T21:21:45.992000+00:00", "url": "https://github.com/wvllxe/CVE-2026-104356-pictshare-weak-delete-code" }, "trigger_signal": { "at": "2026-10-01T21:21:45.992000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-01T21:21:45.992000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-104356" } } }
published 2026-10-01 22:04Z
last change 2026-10-21 17:00Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.