CVE-2026-117564

waiting for further signals

EUVD-2026-110842 ↗

no check availablenot proven exploitable

cve.orgpublic pockev

buqiyuan nest-admin < 1.0.1

fixed in 1.0.1

CWE-321 Use of Hard-coded Cryptographic Key

ETK-2026-2764, permanent identifier

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

4h 42msince last run

31mAI analysis

timeline

0 = cve.org publication

trigger signal (cve.org) +0hwaiting for further signals+1h22m

+2h

+4h

+6h

+8h

+10h

+12h

description

nest-admin releases before 1.0.1 include an exposed JWT signing secret that can allow attacker-created credentials to pass authorization checks. An unauthenticated party able to reach a deployment that accepts these tokens may gain administrative access.

mitigation

Upgrade nest-admin to version 1.0.1 or later. Rotate the JWT signing secret and invalidate existing tokens after upgrading.

fixed in 1.0.1

check

exploit

automation

–

auth required

EPSS

–

agent run time

31m

cve.org record, t = 0

2026-10-27 13:07Z

Δ to public poc

–

Δ to kev

–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

2026-10-27 13:07Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-117564

this entry in the feed

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

{
  "etk_id": "ETK-2026-2764",
  "cve_id": "CVE-2026-117564",
  "display_id": "CVE-2026-117564",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-110842",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in nest-admin",
  "summary": "nest-admin releases before 1.0.1 include an exposed JWT signing secret that can allow attacker-created credentials to pass authorization checks. An unauthenticated party able to reach a deployment that accepts these tokens may gain administrative access.",
  "mitigation": "Upgrade nest-admin to version 1.0.1 or later. Rotate the JWT signing secret and invalidate existing tokens after upgrading.",
  "vendor": "buqiyuan",
  "product": "nest-admin",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.0.1"
      ],
      "package_name": "nest-admin",
      "purl": null
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.7513266,
  "t0_at": "2026-10-27T13:07:58.360000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T13:07:58.360000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T13:07:58.360000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-117564"
    }
  }
}

published 2026-10-27 13:59Z
last change 2026-10-27 18:28Z

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.