CVE-2026-104051

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-10-02. A secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHhigh confidence
EG Risk
57
EG Risk 57/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 1, 2026

Last Modified

October 2, 2026

Advisory Details (2)

Auto-updated Oct 1, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

PictShare < 3.7.1 Sensitive Information Disclosure via info API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pictshare-sensitive-information-disclosure-via-info-api
github_commit

commit ce5fc474e897 (HaschekSolutions/pictshare)

Fix landed in HaschekSolutions/pictshare commit ce5fc474e897 — awaiting tagged release

https://github.com/HaschekSolutions/pictshare/commit/ce5fc474e89769efeae25fee763894bcce3412e3

Vendor Advisories for CVE-2026-104051(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 07:40 UTCEG score recompute
  2. 2026-10-05 07:40 UTCGHSA enrichment
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 19:30 UTCGHSA enrichment
  5. 2026-10-04 07:20 UTCGHSA enrichment
  6. 2026-10-03 19:10 UTCEG score recompute
  7. 2026-10-03 19:10 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 07:01 UTCGHSA enrichment
  10. 2026-10-02 18:51 UTCEG score recompute
  11. 2026-10-02 18:51 UTCGHSA enrichment
  12. 2026-10-02 10:28 UTCEG score recompute
  13. 2026-10-02 10:28 UTCGHSA enrichment
  14. 2026-10-01 22:19 UTCEG score recompute
  15. 2026-10-01 21:21 UTCEG score recompute
  16. 2026-10-01 21:20 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCwvllxe/CVE-2026-104051-pictshare-info-disclosure
    First seen Oct 2, 2026

    Sensitive info disclosure via info API in PictShare < 3.7.1 (CWE-522). PoC + advisory writeup.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-104051?
CVE-2026-104051 is a high vulnerability published on October 1, 2026. PictShare before 3.7.1 contains an information disclosure vulnerability that allows unauthenticated attackers to obtain the secret deletecode and uploader metadata by calling the API::info() endpoint which returns the complete raw metadata object without a field whitelist. Attackers can use the…
When was CVE-2026-104051 disclosed?
CVE-2026-104051 was first published on October 1, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-104051 actively exploited?
CVE-2026-104051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104051?
CVE-2026-104051 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104051?
An upstream fix for CVE-2026-104051 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-104051 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-104051

Explore →

Is Your Infrastructure Affected by CVE-2026-104051?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs