CVE-2026-111472

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

GHSA-jh7x-4h8h-jq6w ↗EUVD-2026-102826 ↗

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.
TSG Profleet >= 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-1759Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 19h 49msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h18m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

TSG Profleet contains an SQL injection vulnerability in its web interface. An attacker who can reach the affected functionality may access or alter data stored in the application's database.

mitigation

Upgrade Profleet to version 16/10/2026 or later. Restrict access to the Profleet web interface to trusted users and networks until the upgrade is complete.

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.
–
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.23%12th percentile
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 08:37Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-16 08:37Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1759",
  "cve_id": "CVE-2026-111472",
  "display_id": "CVE-2026-111472",
  "ghsa_id": "GHSA-jh7x-4h8h-jq6w",
  "euvd_id": "EUVD-2026-102826",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in TSG Profleet",
  "summary": "TSG Profleet contains an SQL injection vulnerability in its web interface. An attacker who can reach the affected functionality may access or alter data stored in the application's database.",
  "mitigation": "Upgrade Profleet to version 16/10/2026 or later. Restrict access to the Profleet web interface to trusted users and networks until the upgrade is complete.",
  "vendor": "TSG",
  "product": "Profleet",
  "affected": [
    {
      "affected_notes": [
        ">= 0, < 16/10/2026"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "16/10/2026"
      ],
      "package_name": "Profleet",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1271,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.34893375,
  "t0_at": "2026-10-16T08:37:34.959000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T08:37:34.959000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T08:37:34.959000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111472"
    }
  }
}

published 2026-10-16 09:24Z
last change 2026-10-21 05:31Z

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.