CVE-2026-123087

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

GHSA-x2hr-mpw9-c694 ↗EUVD-2026-118028 ↗

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.
Atmira SIREC >= 0, < 16/10/2026
fixed in 16/10/2026
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-3710Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 10h 56msince last run
53mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h28m
0
+2h
+6h
+8h
+10h
+12h

description

Atmira SIREC is affected by an SQL injection flaw in its handling of user-supplied JSON data. An attacker able to submit the relevant input may change database query behavior and access unintended information.

mitigation

Upgrade SIREC to version 16/10/2026. Until the upgrade is complete, limit untrusted access to interfaces that accept the relevant JSON input.

fixed in 16/10/2026

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
53m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 09:30Z
Δ 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-11-06 09:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3710",
  "cve_id": "CVE-2026-123087",
  "display_id": "CVE-2026-123087",
  "ghsa_id": "GHSA-x2hr-mpw9-c694",
  "euvd_id": "EUVD-2026-118028",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Atmira SIREC",
  "summary": "Atmira SIREC is affected by an SQL injection flaw in its handling of user-supplied JSON data. An attacker able to submit the relevant input may change database query behavior and access unintended information.",
  "mitigation": "Upgrade SIREC to version 16/10/2026. Until the upgrade is complete, limit untrusted access to interfaces that accept the relevant JSON input.",
  "vendor": "Atmira",
  "product": "SIREC",
  "affected": [
    {
      "affected_notes": [
        ">= 0, < 16/10/2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "16/10/2026"
      ],
      "package_name": "SIREC",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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": 53.10411245,
  "t0_at": "2026-11-06T09:30:48.276000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T09:30:48.276000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T09:30:48.276000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123087"
    }
  }
}

published 2026-11-06 09:50Z
last change 2026-11-07 06:24Z

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.