CVE-2026-134679

validatedZero produced an exploit or a check.

GHSA-2v4f-j5x5-vf33 ↗EUVD-2026-132604 ↗

check availableZero validated a working check for it.proven exploitableZero has validated a full working exploit.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Cirx08 WeddingShare <= 1.8.2
CWE-862 Missing Authorization
ETK-2026-5170Zero's internal tracking ID, independent of the CVE number., permanent identifier
+47mTTV
20mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck + exploit+47m
0
+10min
+20min
+30min
+40min
+50min

description

WeddingShare through 1.8.2 exposes gallery item metadata through an endpoint that does not enforce the gallery secret. An unauthenticated attacker can use the disclosed information to access photos and videos from protected galleries when those files are served statically.

mitigation

Restrict or disable unauthenticated access to the affected gallery-item endpoint, and require authorization before serving gallery media. Until an upstream fix is available, limit public access to WeddingShare and review exposed gallery content.

check
available
exploit
yes
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.
deterministic
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.
–
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-22 02:02Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Differential: the exploit fired on the vulnerable build and stayed silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-22 02:02Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-134679

{
  "etk_id": "ETK-2026-5170",
  "cve_id": "CVE-2026-134679",
  "display_id": "CVE-2026-134679",
  "ghsa_id": "GHSA-2v4f-j5x5-vf33",
  "euvd_id": "EUVD-2026-132604",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in WeddingShare gallery media access",
  "summary": "WeddingShare through 1.8.2 exposes gallery item metadata through an endpoint that does not enforce the gallery secret. An unauthenticated attacker can use the disclosed information to access photos and videos from protected galleries when those files are served statically.",
  "mitigation": "Restrict or disable unauthenticated access to the affected gallery-item endpoint, and require authorization before serving gallery media. Until an upstream fix is available, limit public access to WeddingShare and review exposed gallery content.",
  "vendor": "Cirx08",
  "product": "WeddingShare",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.8.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WeddingShare",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": true,
  "pipeline_minutes": 19.762624383333332,
  "t0_at": "2026-11-22T02:02:36.662000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-22T02:49:43.477751+00:00",
      "days": 0.032717774895833336,
      "is_lower_bound": false,
      "measured_at": "2026-11-22T02:02:36.662000+00:00",
      "url": null
    },
    "exploit": {
      "at": "2026-11-22T02:49:43.477751+00:00",
      "days": 0.032717774895833336,
      "is_lower_bound": false,
      "measured_at": "2026-11-22T02:02:36.662000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-22T02:02:36.662000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-22T02:02:36.662000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-134679"
    }
  }
}

published 2026-11-22 02:29Z
last change 2026-11-22 22:18Z

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.