CVE-2026-104051: PictShare < 3.7.1 Sensitive Information Disclosure via info API

What it is

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.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-01).

Weakness: Insufficiently Protected Credentials

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 4 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 7 references on Exploit Observer

Live scores

EPSS

0.005
low predicted chance of attack

VEDAS

0.985
strong exploit evidence

On CISA KEV

Not listed

Detection rule

Suricata

Who is affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: 3.7.1.

Vendor guidance:

• Patch Commit (issue-tracking, release-notes)
• Vendor Patch (patch)

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-104051 PictShare - Unauthenticated Information Disclosure via info API. Add them to your Suricata rule set and reload.

# CVE-2026-104051 - PictShare (< 3.7.1) unauthenticated information disclosure (CWE-522). The
# API::info() endpoint (GET /api/info/<hash>) returns the raw getMetadataOfHash() object with no
# field whitelist, leaking the secret delete_code alongside the uploader ip, useragent, remote_port
# and sha1. Matches an HTTP response body that exposes delete_code together with the uploader
# remote_port and useragent fields, the combination returned only by the unfiltered info() object.
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-104051 PictShare - Unauthenticated Information Disclosure via info API"; flow:established,to_client; file.data; content:"delete_code"; nocase; fast_pattern; content:"remote_port"; nocase; content:"useragent"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-104051; reference:url,https://www.exploit.observer/?keyword=CVE-2026-104051&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=pictshare&match=exact; sid:1092802; rev:1;)

CVE-2026-104051.rules on GitHub

References

Vendor advisories and patches

• Patch Commit (issue-tracking, release-notes)
• Vendor Patch (patch)

Technical analysis and advisories

• VulnCheck Advisory (third-party-advisory)

Other databases

• CVE record (cve.org)
• NVD
• Exploit Observer

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.