Skip to content

v1.4

Choose a tag to compare

@righel righel released this 26 Oct 10:59
· 2 commits to main since this release
v1.4
26fd478

Security fixes and hardening after the review of the Common Criteria EAL 2 evaluation against the code. The evaluation document is updated to revision 1.4, targeting this release.

⚠️ Breaking change

Sightings synchronization is now disabled by default. Deployments synchronizing sightings must set "allow_sightings": true on the destination instances (#29).

Security fixes

Severity Description PR CVE
Medium Feed responses with a successful status code other than 200 (e.g. 203, 206) were forwarded without being filtered. #24 CVE-2026-116372
Low An event holding an allowed and a non-allowed tag of a required taxonomy (e.g. tlp:clear + tlp:amber) was forwarded. #23 CVE-2026-118173
Low Attribute categories and required taxonomies tags were matched case sensitively (completes ID 004). #27 CVE-2026-116469

What's Changed

  • fix: [security] enforce allowed tags on every tag of a required taxonomy, attributes of an event inherit its required taxonomies in #23
  • fix: [security] block successful feed responses other than 200 in #24
  • fix: allow feed events holding objects, event reports or analyst data without distribution level in #25
  • chg: keep one year of rotated logs by default in #26
  • fix: [security] match categories and required taxonomies regardless of case in #27
  • chg: log allowed flows and request sources, log shutdown, keep the last valid config on invalid reload, watch the config file directory in #28
  • chg: [breaking] sightings synchronization requires the allow_sightings setting in #29
  • chg: Common Criteria EAL 2 evaluation document revision 1.4 in #30

Upgrade notes

  • Add "allow_sightings": true to the instances that should receive sightings.
  • src/logging.yaml now keeps 365 daily logs, deployments with their own logging.yaml are not affected.

Full Changelog: v1.3...v1.4