Skip to content

CVE-2026-31368: Database Initialization Failure

A critical stability failure has been identified within the OpenCVE management command import_cves. This flaw prevents the successful initialization of the threat intelligence database on fresh installations, rendering the platform effectively unusable for security operations until resolved. The root cause lies in improper handling of data structures during the parsing of the OpenCVE KB repository.

Analysis indicates that the failure occurs during the processing of CVE data entries. The import_cves.py file, specifically within the insert_cve method, attempts to access nested keys in the dictionary object representing individual CVE entries.

The code at line 44 of /app/opencve/web/cves/management/commands/import_cves.py executes: "created": cve_data["created"]["data"]

When a CVE entry lacks the “created” key, or the “created” entry is null, the application attempts to subscript a NoneType object, triggering a TypeError. This vulnerability is not an arbitrary code execution vector, but rather an availability failure that prevents the system from populating its core database.

To monitor for this failure in production environments, the following detection strategies should be implemented.

title: OpenCVE Import Failure Detected
logsource:
product: linux
service: docker
detection:
selection:
Message|contains:
- "TypeError: 'NoneType' object is not subscriptable"
- "import_cves.py"
condition: selection