Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2026-42031

ckan SQL Injection

Ckan / ckan · >= 2.11.0, < 2.11.5

View live feed Monitor via API Watch CVE-2026-42031
Severity
CVSS 8.3 · High
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
1.8%
First observed
07 Sep 2026
Last observed
10 Sep 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-42031 is an unauthenticated vulnerability affecting Ckan ckan. CKAN is an open-source DMS (data management system) for powering data hubs and data portals. Prior to 2.10.10 and 2.11.5, a vulnerability in...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence.

Who is affected?

Ckan / ckan >= 2.11.0, < 2.11.5.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

CKAN is an open-source DMS (data management system) for powering data hubs and data portals

CKAN is an open-source DMS (data management system) for powering data hubs and data portals.

Prior to 2.10.10 and 2.11.5, a vulnerability in datastore_search_sql allowed attackers to inject SQL in order to gain access to private resources and PostgreSQL system information This vulnerability is fixed in 2.10.10 and 2.11.5.

Vendor Product Affected Status
ckan ckan >= 2.11.0, < 2.11.5 Affected
ckan ckan Before 2.10.10 Affected
Published
13 May 2026
Exploited Since
07 Sep 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

postgresql nuclei_scanner

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

Previdian

Recorded 10 Sep 2026

Previdian independently recorded this as exploited after first seeing it in honeypot sensors.

Active exploitation observed

Previdian sensor

First observed 07 Sep 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
Previdian First 2026-09-10 09:03 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

7

Attempts observed

1

Unique attacker IPs

1

Attacker countries

ER

7

Sensors observed

CVE-2026-42031 exploitation attempts over the last 7 days

Daily events observed by Previdian sensors

Updated 11 Sep 2026

0
0
1
0
2
4
0
5 Sep 6 Sep 7 Sep 8 Sep 9 Sep 10 Sep 11 Sep

First observed 07 Sep 2026 · Last observed 10 Sep 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Request telemetry access

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
1
1
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Scanner Reference Detected
Nuclei https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-42031.yaml 01 Jun 2026

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

8.3 High
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

EPSS

1.8%

Weaknesses

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') CWE-89

All CVSS Scores

CVSS v4.0 8.3 High

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS v3.1 9.8 Critical

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

ddrvahandzo90-hue/CVE-2026-42031-SQL-Injection-Scanner

github · Created 2026-09-07 05:08:05 UTC · 0 stars · AI assessment 85%

CVE-2026-42031 SQL Injection Scanner for CKAN DataStore

CKAN DataStore SQL Search - SQL Injection

nuclei · Created Unknown

Timeline

From disclosure to observed exploitation

  1. Indicator of compromise added

    Indicators of compromise recorded

  2. Observed by Previdian sensors

    Evidence-backed exploitation signal

  3. Public PoC available

    Public proof-of-concept code published

  4. Nuclei template available

    Scanner coverage available

  5. CVE published

    Vulnerability disclosed publicly

  6. CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

View Pro pricing Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-42031

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2026-42031",
  "confidence": "Confirmed",
  "cvss_score": 8.3,
  "cvss_estimated": false,
  "epss_score": 0.01817,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 7, "sensors": 7 }
}