CVE-2026-116620

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

GHSA-xfhf-c35f-773q ↗EUVD-2026-110567 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.
Tencent RapidJSON 1.0; 1.1.0
ETK-2026-2721Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 35msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+0hwaiting for further signals+4h18m
0
+2h
+6h
+8h
+10h
+12h

description

Tencent RapidJSON versions through 1.1.0 contain an out-of-bounds read in regex parsing functionality. A remote attacker may be able to trigger the issue if they can cause an application to process untrusted data through that functionality; the precise triggering conditions are not established by the evidence.

mitigation

Prevent untrusted remote data from reaching RapidJSON regex parsing paths, and isolate services that must handle such data. No fixed release is identified in the evidence; monitor upstream and update to a maintained release containing a correction when one is available.

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
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 00:30Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+0m
Δ 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-27 00:30Z
    ghsa: trigger signal, started the run
  2. 2026-10-27 00:30Z
  3. 2026-10-27 05:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2721",
  "cve_id": "CVE-2026-116620",
  "display_id": "CVE-2026-116620",
  "ghsa_id": "GHSA-xfhf-c35f-773q",
  "euvd_id": "EUVD-2026-110567",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in Tencent RapidJSON regex parsing",
  "summary": "Tencent RapidJSON versions through 1.1.0 contain an out-of-bounds read in regex parsing functionality. A remote attacker may be able to trigger the issue if they can cause an application to process untrusted data through that functionality; the precise triggering conditions are not established by the evidence.",
  "mitigation": "Prevent untrusted remote data from reaching RapidJSON regex parsing paths, and isolate services that must handle such data. No fixed release is identified in the evidence; monitor upstream and update to a maintained release containing a correction when one is available.",
  "vendor": "Tencent",
  "product": "RapidJSON",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0",
        "1.1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "RapidJSON",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.996535733333333,
  "t0_at": "2026-10-27T00:30:22.548000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-27T00:30:22.548000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T00:30:22.548000+00:00",
      "url": "https://github.com/Tencent/rapidjson/issues/2401"
    },
    "trigger_signal": {
      "at": "2026-10-27T00:30:22.548000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T00:30:22.548000+00:00",
      "url": "https://github.com/advisories/GHSA-xfhf-c35f-773q"
    }
  }
}

published 2026-10-27 04:31Z
last change 2026-10-27 07:10Z

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.