High · CVSS 8.8CVE-2026-104051

PictShare < 3.7.1 Sensitive Information Disclosure via info API

Answer in brief

CVE-2026-104051 records a High severity (CVSS 8.8) vulnerability in PictShare < 3.7.1 Sensitive Information Disclosure via info API. The current sources do not mark it as known exploited. The current feed maps HaschekSolutions/pictshare (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 1, 2026Updated Oct 1, 2026Source checked Oct 2, 2026First seen by HOL Oct 1, 2026Material review Oct 1, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.8
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps HaschekSolutions/pictshare (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
HaschekSolutions/pictsharegeneric	>=2.0.0 <3.7.1	3.7.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for HaschekSolutions/pictshare.
Review the reported fix. Update HaschekSolutions/pictshare to 3.7.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 1, 2026

Sources and claim methodology

Upstream source description

PictShare before 3.7.1 contains an information disclosure vulnerability that allows unauthenticated attackers to obtain the secret delete_code and uploader metadata by calling the API::info() endpoint which returns the complete raw metadata object without a field whitelist. Attackers can use the publicly visible file hash to retrieve the delete_code via the info API and then invoke the delete API to permanently delete arbitrary files, while also exposing uploader IP, User Agent, remote port, and SHA-1 hash, resulting in loss of content integrity, availability, and uploader privacy.

Quoted source text, attributed separately from HOL analysis.