CVE-2026-77470

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

GHSA-476v-jr53-8rxc ↗EUVD-2026-102196 ↗

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.7.0
fixed in > 7.7.0
CWE-20 Improper Input Validation
ETK-2026-1701Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:composer/lychee-org/lychee
3d 06h 15msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+53h56m
0
+2h
+4h
+6h
+8h
+10h

description

Lychee releases before 7.7.1 may allow unauthenticated shoppers to alter payment parameters during webshop checkout. An attacker may cause an affected payment gateway to accept a lower payment for automatically fulfilled goods when the webshop is enabled, an item is available for purchase, and a non-PayPal Omnipay gateway is configured.

mitigation

Upgrade lychee-org/lychee to > 7.7.0 or later.

fixed in > 7.7.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.45%37th percentile
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 16:36Z
Δ 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:36Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1701",
  "cve_id": "CVE-2026-77470",
  "display_id": "CVE-2026-77470",
  "ghsa_id": "GHSA-476v-jr53-8rxc",
  "euvd_id": "EUVD-2026-102196",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated payment parameter override in Lychee webshop",
  "summary": "Lychee releases before 7.7.1 may allow unauthenticated shoppers to alter payment parameters during webshop checkout. An attacker may cause an affected payment gateway to accept a lower payment for automatically fulfilled goods when the webshop is enabled, an item is available for purchase, and a non-PayPal Omnipay gateway is configured.",
  "mitigation": "Upgrade lychee-org/lychee to > 7.7.0 or later.",
  "vendor": "LycheeOrg",
  "product": "Lychee",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 7.7.0"
      ],
      "ecosystem": "composer",
      "fixed_versions": [
        "> 7.7.0"
      ],
      "package_name": "lychee-org/lychee",
      "purl": "pkg:composer/lychee-org/lychee"
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0045,
  "epss_percentile": 0.3792,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.88252431666667,
  "t0_at": "2026-10-15T16:36:09.597000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T16:36:09.597000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T16:36:09.597000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-77470"
    }
  }
}

published 2026-10-15 17:53Z
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.