Skip to content

Enable CISA KEV connector to upsert KEV flag on existing CVEs#6484

Closed
Copilot wants to merge 2 commits into
masterfrom
copilot/fix-cisa-kev-connector-update
Closed

Enable CISA KEV connector to upsert KEV flag on existing CVEs#6484
Copilot wants to merge 2 commits into
masterfrom
copilot/fix-cisa-kev-connector-update

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 21, 2026

The CISA KEV connector set x_opencti_cisa_kev=true when creating Vulnerability entities, but did not persist that flag for CVEs already present in OpenCTI from other ingestion paths. This change ensures KEV tagging is applied consistently to existing Vulnerability records as well.

  • Behavior change: send bundles in update mode

    • Updated the CISA KEV connector bundle submission path to use upsert semantics, so incoming Vulnerability objects with deterministic IDs can update existing entities (including x_opencti_cisa_kev) instead of only creating new ones.
  • Scope

    • Single, targeted change in connector send path; no expansion of enrichment surface or relationship/model logic.
self.helper.send_stix2_bundle(
    serialized_bundle,
    work_id=work_id,
    update=True,
)

Copilot AI changed the title [WIP] Fix CISA KEV connector not updating x_opencti_cisa_kev field Enable CISA KEV connector to upsert KEV flag on existing CVEs May 21, 2026
Copilot AI requested a review from SamuelHassine May 21, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CISA KEV Connector does not update x_opencti_cisa_kev when CVE is already in the platform

2 participants