CVE-2026-120209

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

GHSA-p83w-vf54-73v4 ↗EUVD-2026-114730 ↗

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.
anji-plus AJ-Report <= 1.7.1
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-3193Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 59msince last run
46mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h54m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

AJ-Report through 1.7.1 uses a built-in secret to sign report-sharing tokens. An attacker who can reach the affected service may forge accepted tokens and access an unauthenticated script-processing function, potentially executing code on the server.

mitigation

Restrict AJ-Report to trusted networks and authenticated users, and prevent public access to report-sharing and script-processing functions. Monitor for a vendor update; no fixed version is recorded in the available advisory data.

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.
–
agent run time
46m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-31 17: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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-31 17:25Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3193",
  "cve_id": "CVE-2026-120209",
  "display_id": "CVE-2026-120209",
  "ghsa_id": "GHSA-p83w-vf54-73v4",
  "euvd_id": "EUVD-2026-114730",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hard-coded JWT signing key in AJ-Report",
  "summary": "AJ-Report through 1.7.1 uses a built-in secret to sign report-sharing tokens. An attacker who can reach the affected service may forge accepted tokens and access an unauthenticated script-processing function, potentially executing code on the server.",
  "mitigation": "Restrict AJ-Report to trusted networks and authenticated users, and prevent public access to report-sharing and script-processing functions. Monitor for a vendor update; no fixed version is recorded in the available advisory data.",
  "vendor": "anji-plus",
  "product": "AJ-Report",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.7.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "AJ-Report",
      "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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 45.87582985,
  "t0_at": "2026-10-31T17:25:56.161000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T17:25:56.161000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T17:25:56.161000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-120209"
    }
  }
}

published 2026-10-31 17:34Z
last change 2026-10-31 21:57Z

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.