CVE-2026-107852

waiting for further signals

GHSA-rf56-676w-hj4g ↗EUVD-2026-95982 ↗

no check availablenot proven exploitable

cve.orgpublic pockev

Jexactyl <= 4.0.1

CWE-345 Insufficient Verification of Data Authenticity

ETK-2026-1129, permanent identifier

pkg:composer/jexactyl/jexactyl

cvss7.1cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

10d 00h 02msince last run

44mAI analysis

timeline

0 = cve.org publication

trigger signal (cve.org) +0hwaiting for further signals+33h17m

+2h

+4h

+6h

+8h

+10h

description

Jexactyl versions before 4.0.5 do not verify that a completed Stripe Checkout Session matches the associated order's amount and currency. An authenticated client may cause an order to be processed for less than its required price when Stripe billing is enabled and a Stripe secret key is configured.

mitigation

Upgrade Jexactyl to version 4.0.5 or later. Until upgrading, disable the billing module or Stripe billing integration where practical.

check

exploit

automation

contextual

auth required

yes, low privileges

EPSS

0.16%4th percentile

agent run time

44m

cve.org record, t = 0

2026-10-09 20:28Z

Δ to public poc

–

Δ to kev

–

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.

2026-10-09 20:28Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-107852

this entry in the feed

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

{
  "etk_id": "ETK-2026-1129",
  "cve_id": "CVE-2026-107852",
  "display_id": "CVE-2026-107852",
  "ghsa_id": "GHSA-rf56-676w-hj4g",
  "euvd_id": "EUVD-2026-95982",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Payment amount validation flaw in Jexactyl billing",
  "summary": "Jexactyl versions before 4.0.5 do not verify that a completed Stripe Checkout Session matches the associated order's amount and currency. An authenticated client may cause an order to be processed for less than its required price when Stripe billing is enabled and a Stripe secret key is configured.",
  "mitigation": "Upgrade Jexactyl to version 4.0.5 or later. Until upgrading, disable the billing module or Stripe billing integration where practical.",
  "vendor": "Jexactyl",
  "product": "Jexactyl",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 4.0.1"
      ],
      "ecosystem": "composer",
      "fixed_versions": [],
      "package_name": "jexactyl/jexactyl",
      "purl": "pkg:composer/jexactyl/jexactyl"
    }
  ],
  "cwes": [
    345
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N",
  "epss_score": 0.0016,
  "epss_percentile": 0.0483,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.00518461666667,
  "t0_at": "2026-10-09T20:28:06.513000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T20:28:06.513000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T20:28:06.513000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107852"
    }
  }
}

published 2026-10-10 03:32Z
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.