CVE-2026-112309

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

GHSA-ffhp-5372-ccmj ↗EUVD-2026-104401 ↗

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.
airjp73 @rvf/set-get < 7.0.4
fixed in 7.0.4
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
ETK-2026-2063Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 00h 37msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h45m
0
+2h
+6h
+8h
+10h
+12h

description

@rvf/set-get versions earlier than 7.0.4 are affected by prototype pollution in path-setting logic. An unauthenticated remote party may cause process-wide denial of service when the application accepts form data through @rvf/core.

mitigation

Upgrade @rvf/set-get to version 7.0.4 or later. Until upgraded, restrict unauthenticated form submissions that reach @rvf/core parsing.

fixed in 7.0.4

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.
0.40%32nd percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 15:28Z
Δ 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: 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.

  1. 2026-10-19 15:28Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2063",
  "cve_id": "CVE-2026-112309",
  "display_id": "CVE-2026-112309",
  "ghsa_id": "GHSA-ffhp-5372-ccmj",
  "euvd_id": "EUVD-2026-104401",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Prototype pollution in @rvf/set-get",
  "summary": "@rvf/set-get versions earlier than 7.0.4 are affected by prototype pollution in path-setting logic. An unauthenticated remote party may cause process-wide denial of service when the application accepts form data through @rvf/core.",
  "mitigation": "Upgrade @rvf/set-get to version 7.0.4 or later. Until upgraded, restrict unauthenticated form submissions that reach @rvf/core parsing.",
  "vendor": "airjp73",
  "product": "@rvf/set-get",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 7.0.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.0.4"
      ],
      "package_name": "@rvf/set-get",
      "purl": null
    }
  ],
  "cwes": [
    1321
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.004,
  "epss_percentile": 0.323,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.696055333333334,
  "t0_at": "2026-10-19T15:28:58.442000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T15:28:58.442000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T15:28:58.442000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112309"
    }
  }
}

published 2026-10-19 16:08Z
last change 2026-10-21 16:15Z

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.