Vulnerability report

Exploitation Attempts Observed Confirmed Confidence Not in CISA KEV

CVE-2026-42031

ckan SQL Injection

Ckan · >= 2.11.0, < 2.11.5

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 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...

Have exploitation attempts been observed?

Yes. Previdian sensors have observed 7 exploitation attempts, 1 unique attacker IP, and 1 country targeting CVE-2026-42031. First observed Sep 07, 2026; last observed Sep 10, 2026. Confidence is confirmed.

Who is affected?

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.

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

Tags

postgresql nuclei_scanner

CVE References

Exploitation evidence

Evidence of exploitation attempts

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

Exploitation Attempts Observed in the Wild

Previdian

Recorded 10 Sep 2026

Previdian sensors observed exploitation attempts targeting this vulnerability.

Exploitation Attempts Observed

Previdian sensor

First observed 07 Sep 2026

Previdian sensors observed exploitation attempts targeting this vulnerability.

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 Sensors First 2026-09-10 09:03 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

Previdian Sensor Observations

Previdian sensor observations are exploitation attempts targeting this vulnerability. They do not show that the target was vulnerable or that the attempt succeeded. 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 55 days

Daily events observed by Previdian sensors

Updated 30 Oct 2026

0
1
0
2
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
6 Sep 17 Sep 28 Sep 9 Oct 30 Oct

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.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

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

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.

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

8.3 High

Potential damage if exploited. Separate from whether attackers are using it.

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%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

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

Timeline

From disclosure to observed exploitation attempts

  1. 19:30 UTC

    Indicator of compromise added

    Indicators of compromise recorded

  2. 19:30 UTC

    Observed by Previdian sensors

    Previdian sensors observed exploitation attempts targeting this vulnerability.

  3. 14:21 UTC

    Public PoC available

    Public proof-of-concept code published

  4. 15:34 UTC

    Nuclei template available

    Scanner coverage available

  5. 18:52 UTC

    CVE published

    Vulnerability disclosed publicly

  6. 16:05 UTC

    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.

  • 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

Sample API response
{
  "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 }
}