CVE-2026-61611

waiting for further signalsZero needs more public information before it can validate it.

GHSA-48vf-fwx6-2ph6 ↗EUVD-2026-102189 ↗

no check availablenot proven exploitable
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.
LycheeOrg Lychee <= 7.6.0
fixed in > 7.6.0
CWE-307 Improper Restriction of Excessive Authentication Attempts
ETK-2026-1709Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:composer/lychee-org/lychee
5d 09h 37msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Lychee versions before 7.6.1 do not limit repeated password attempts when unlocking protected albums. An unauthenticated remote attacker with an album identifier may automate password guessing and access private photos if the album password is recovered.

mitigation

Upgrade Lychee to version 7.6.1 or later. Restrict public access to protected album endpoints until the update is deployed.

fixed in > 7.6.0

check
no
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.35%27th percentile
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 16:25Z
Δ 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

Contextual: an exploit technique exists, 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.

  1. 2026-10-15 16:25Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1709",
  "cve_id": "CVE-2026-61611",
  "display_id": "CVE-2026-61611",
  "ghsa_id": "GHSA-48vf-fwx6-2ph6",
  "euvd_id": "EUVD-2026-102189",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing password-attempt throttling in Lychee albums",
  "summary": "Lychee versions before 7.6.1 do not limit repeated password attempts when unlocking protected albums. An unauthenticated remote attacker with an album identifier may automate password guessing and access private photos if the album password is recovered.",
  "mitigation": "Upgrade Lychee to version 7.6.1 or later. Restrict public access to protected album endpoints until the update is deployed.",
  "vendor": "LycheeOrg",
  "product": "Lychee",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 7.6.0"
      ],
      "ecosystem": "composer",
      "fixed_versions": [
        "> 7.6.0"
      ],
      "package_name": "lychee-org/lychee",
      "purl": "pkg:composer/lychee-org/lychee"
    }
  ],
  "cwes": [
    307
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0035,
  "epss_percentile": 0.2737,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.70104645,
  "t0_at": "2026-10-15T16:25:24.968000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T16:25:24.968000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T16:25:24.968000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-61611"
    }
  }
}

published 2026-10-15 18:36Z
last change 2026-10-21 04:45Z

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.