← back to feed
CVE-2026-65874

CVE-2026-65874

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

GHSA-7pvg-2h32-c6jc ↗EUVD-2026-113749 ↗

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.
Apache Software Foundation Apache Fineract <= 1.15.0
ETK-2026-3066Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 56msince last run
1h 11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h34m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Fineract through version 1.15.0 is affected in center and datatable read APIs. An authenticated user with relevant read permissions may influence database queries through sorting-related request inputs, enabling blind SQL injection.

mitigation

Upgrade Apache Fineract to version 1.16.1. Until upgraded, restrict read access to the affected center and datatable endpoints to trusted users.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 08:18Z
Δ 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-30 08:18Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-7pvg-2h32-c6jc
  2. 2026-10-30 08:18Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3066",
  "cve_id": "CVE-2026-65874",
  "display_id": "CVE-2026-65874",
  "ghsa_id": "GHSA-7pvg-2h32-c6jc",
  "euvd_id": "EUVD-2026-113749",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Apache Fineract read endpoints",
  "summary": "Apache Fineract through version 1.15.0 is affected in center and datatable read APIs. An authenticated user with relevant read permissions may influence database queries through sorting-related request inputs, enabling blind SQL injection.",
  "mitigation": "Upgrade Apache Fineract to version 1.16.1. Until upgraded, restrict read access to the affected center and datatable endpoints to trusted users.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Fineract",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.15.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Fineract",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 70.95781453333333,
  "t0_at": "2026-10-30T08:18:08.619000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T08:18:08.619000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T08:18:08.619000+00:00",
      "url": "https://github.com/advisories/GHSA-7pvg-2h32-c6jc"
    }
  }
}

published 2026-10-30 09:41Z
last change 2026-10-30 13:29Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.