CVE-2026-129143

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

GHSA-xg9q-98hr-3xwm ↗EUVD-2026-125617 ↗

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.
itwanger paicoding 1.0.3
ETK-2026-4415Zero's internal tracking ID, independent of the CVE number., permanent identifier
9h 48msince last run
54mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h18m
0
+4h
+6h
+8h
+10h
+12h

description

paicoding 1.0.3 does not enforce authorization for article-detail access. An unauthenticated remote party can view content intended to be restricted when the affected endpoint is reachable.

mitigation

Require authentication and enforce entitlement checks before returning article details; restrict network access to the endpoint until this is in place. The evidence does not identify a fixed release, so validate any upgrade against the authorization requirement.

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.
–
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
54m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 17:22Z
Δ 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

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.

  1. 2026-11-13 17:22Z
    ghsa: trigger signal, started the run
  2. 2026-11-13 17:22Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4415",
  "cve_id": "CVE-2026-129143",
  "display_id": "CVE-2026-129143",
  "ghsa_id": "GHSA-xg9q-98hr-3xwm",
  "euvd_id": "EUVD-2026-125617",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in paicoding article detail access",
  "summary": "paicoding 1.0.3 does not enforce authorization for article-detail access. An unauthenticated remote party can view content intended to be restricted when the affected endpoint is reachable.",
  "mitigation": "Require authentication and enforce entitlement checks before returning article details; restrict network access to the endpoint until this is in place. The evidence does not identify a fixed release, so validate any upgrade against the authorization requirement.",
  "vendor": "itwanger",
  "product": "paicoding",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "paicoding",
      "purl": null
    }
  ],
  "cwes": null,
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 53.581946683333335,
  "t0_at": "2026-11-13T17:22:07.496000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T17:22:07.496000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T17:22:07.496000+00:00",
      "url": "https://github.com/advisories/GHSA-xg9q-98hr-3xwm"
    }
  }
}

published 2026-11-13 18:45Z
last change 2026-11-14 03:12Z

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.