CVE-2026-95610

validatedZero produced an exploit or a check.

GHSA-c4q9-w4vh-p5h8 ↗EUVD-2026-95596 ↗

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.+18d
UpSolution Core <= 9.3
ETK-2026-2770Zero's internal tracking ID, independent of the CVE number., permanent identifier
+18dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
cve.org publicationtrigger signal +18dkev+18dcheck availableagent stopped
0
+5d
+10d
+15d
+20d

description

UpSolution Core us-core through version 9.3 is affected by a blind SQL injection vulnerability. An authenticated attacker may be able to send crafted application input that causes unintended database queries.

mitigation

Update to a vendor-provided release newer than 9.3 when one is available; no fixed version is recorded in the advisory. Until then, restrict access to authenticated administrative or application functions and limit the database account's permissions.

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.
yes, low privileges
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-09 10:00Z
Δ 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.
+18d

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-09 10:00Z
  2. 2026-10-27
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-27 00:00Z
  4. 2026-10-27 14:46Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2770",
  "cve_id": "CVE-2026-95610",
  "display_id": "CVE-2026-95610",
  "ghsa_id": "GHSA-c4q9-w4vh-p5h8",
  "euvd_id": "EUVD-2026-95596",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Blind SQL injection in UpSolution Core us-core",
  "summary": "UpSolution Core us-core through version 9.3 is affected by a blind SQL injection vulnerability. An authenticated attacker may be able to send crafted application input that causes unintended database queries.",
  "mitigation": "Update to a vendor-provided release newer than 9.3 when one is available; no fixed version is recorded in the advisory. Until then, restrict access to authenticated administrative or application functions and limit the database account's permissions.",
  "vendor": "UpSolution",
  "product": "UpSolution Core",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 9.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "us-core",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.5,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.013117383333333333,
  "t0_at": "2026-10-09T10:00:17.308000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-27T14:46:42.214988+00:00",
      "days": 18.198899386435187,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T10:00:17.308000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-27T00:00:00+00:00",
      "days": 18,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T10:00:17.308000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-95610"
    },
    "trigger_signal": {
      "at": "2026-10-27T00:00:00+00:00",
      "days": 17.58313300925926,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T10:00:17.308000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-95610"
    }
  }
}

published 2026-10-27 14:46Z
last change 2026-10-27 19: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.