CVE-2026-116863

validatedZero produced an exploit or a check.

GHSA-r394-jh8x-rp4v ↗EUVD-2026-111144 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Tribulant Software Newsletters <= 4.18.2
ETK-2026-2796Zero's internal tracking ID, independent of the CVE number., permanent identifier
+5h24mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+5h24magent stopped
0
+2h
+4h
+6h

description

Tribulant Software Newsletters versions through 4.18.2 are affected by a cross-site request forgery flaw. An attacker may be able to cause actions in the application when they can persuade a user with an active session to visit attacker-controlled content.

mitigation

Update Newsletters to a vendor release later than 4.18.2 after confirming that it addresses this issue. Until an update is available, disable the component where feasible and restrict access to the affected site's administrative interface.

check
available
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.
deterministic
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
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 15:56Z
Δ 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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-10-27 15:56Z
    ghsa: trigger signal, started the run
  2. 2026-10-27 15:56Z
  3. 2026-10-27 21:21Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2796",
  "cve_id": "CVE-2026-116863",
  "display_id": "CVE-2026-116863",
  "ghsa_id": "GHSA-r394-jh8x-rp4v",
  "euvd_id": "EUVD-2026-111144",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site request forgery in Tribulant Newsletters",
  "summary": "Tribulant Software Newsletters versions through 4.18.2 are affected by a cross-site request forgery flaw. An attacker may be able to cause actions in the application when they can persuade a user with an active session to visit attacker-controlled content.",
  "mitigation": "Update Newsletters to a vendor release later than 4.18.2 after confirming that it addresses this issue. Until an update is available, disable the component where feasible and restrict access to the affected site's administrative interface.",
  "vendor": "Tribulant Software",
  "product": "Newsletters",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.18.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "newsletters-lite",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.01290505,
  "t0_at": "2026-10-27T15:56:41.312000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-27T21:21:03.401151+00:00",
      "days": 0.22525566146990741,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T15:56:41.312000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-27T15:56:41.312000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T15:56:41.312000+00:00",
      "url": "https://github.com/advisories/GHSA-r394-jh8x-rp4v"
    }
  }
}

published 2026-10-27 21:20Z
last change 2026-10-27 21:33Z

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.