Skip to content

FEATURE: Informix Database Connection Config#26072

Merged
ulixius9 merged 13 commits intoopen-metadata:mainfrom
akashverma0786:feature/informix-database-connector
Mar 13, 2026
Merged

FEATURE: Informix Database Connection Config#26072
ulixius9 merged 13 commits intoopen-metadata:mainfrom
akashverma0786:feature/informix-database-connector

Conversation

@akashverma0786
Copy link
Collaborator

@akashverma0786 akashverma0786 commented Feb 24, 2026

Describe your changes:

Fixes

I worked on ... because ...

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Summary by Gitar

  • Informix database support:
    • Added InformixConnection schema with SSL configuration and server name settings
    • Registered InformixTableMetricComputer to read metrics from systables catalog
    • Added Dialects.Informix enum value for database dialect identification
  • Profiler metric implementations:
    • Implemented MedianFn compiler for Informix using ROW_NUMBER window functions
    • Added SumFn compiler handling DECIMAL precision and DATETIME type edge cases
    • Configured LenFn, ModuloFn, and column count functions with literal binds to avoid JDBC bind parameters
  • Configuration and UI:
    • Created Informix test connection JSON with validation steps
    • Added Informix to beta services list and generated TypeScript connection types
    • Added is_blob() helper for detecting binary/text columns unsuitable for profiling

This will update automatically on new commits.

@github-actions
Copy link
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

…into feature/informix-database-connector
@github-actions
Copy link
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2026

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2026

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

🛡️ TRIVY SCAN RESULT 🛡️

Target: openmetadata-ingestion-base-slim:trivy (debian 12.13)

Vulnerabilities (247)

Package Vulnerability ID Severity Installed Version Fixed Version
imagemagick CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6-common CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
imagemagick-6.q16 CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-arch-config CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6-headers CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6 CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-6-extra CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-6.q16-dev CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickcore-dev CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6-headers CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-6 CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-6.q16-dev CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25897 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25898 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25968 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25983 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25986 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25987 🔥 CRITICAL 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-24481 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-24485 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25795 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25796 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25799 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25965 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25970 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25988 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-25989 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-26066 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-26283 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7
libmagickwand-dev CVE-2026-27798 🚨 HIGH 8:6.9.11.60+dfsg-1.6+deb12u6 8:6.9.11.60+dfsg-1.6+deb12u7

🛡️ TRIVY SCAN RESULT 🛡️

Target: Java

Vulnerabilities (37)

Package Vulnerability ID Severity Installed Version Fixed Version
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.12.7 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.12.7 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.13.4 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.13.4 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.15.2 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-databind CVE-2022-42003 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4.2
com.fasterxml.jackson.core:jackson-databind CVE-2022-42004 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4
com.google.code.gson:gson CVE-2022-25647 🚨 HIGH 2.2.4 2.8.9
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.3.0 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.3.0 3.25.5, 4.27.5, 4.28.2
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.7.1 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.7.1 3.25.5, 4.27.5, 4.28.2
com.nimbusds:nimbus-jose-jwt CVE-2023-52428 🚨 HIGH 9.8.1 9.37.2
com.squareup.okhttp3:okhttp CVE-2021-0341 🚨 HIGH 3.12.12 4.9.2
commons-beanutils:commons-beanutils CVE-2025-48734 🚨 HIGH 1.9.4 1.11.0
commons-io:commons-io CVE-2024-47554 🚨 HIGH 2.8.0 2.14.0
dnsjava:dnsjava CVE-2024-25638 🚨 HIGH 2.1.7 3.6.0
io.airlift:aircompressor CVE-2025-67721 🚨 HIGH 0.27 2.0.3
io.netty:netty-codec-http2 CVE-2025-55163 🚨 HIGH 4.1.96.Final 4.2.4.Final, 4.1.124.Final
io.netty:netty-codec-http2 GHSA-xpw8-rcwv-8f8p 🚨 HIGH 4.1.96.Final 4.1.100.Final
io.netty:netty-handler CVE-2025-24970 🚨 HIGH 4.1.96.Final 4.1.118.Final
net.minidev:json-smart CVE-2021-31684 🚨 HIGH 1.3.2 1.3.3, 2.4.4
net.minidev:json-smart CVE-2023-1370 🚨 HIGH 1.3.2 2.4.9
org.apache.avro:avro CVE-2024-47561 🔥 CRITICAL 1.7.7 1.11.4
org.apache.avro:avro CVE-2023-39410 🚨 HIGH 1.7.7 1.11.3
org.apache.derby:derby CVE-2022-46337 🔥 CRITICAL 10.14.2.0 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0
org.apache.ivy:ivy CVE-2022-46751 🚨 HIGH 2.5.1 2.5.2
org.apache.mesos:mesos CVE-2018-1330 🚨 HIGH 1.4.3 1.6.0
org.apache.thrift:libthrift CVE-2019-0205 🚨 HIGH 0.12.0 0.13.0
org.apache.thrift:libthrift CVE-2020-13949 🚨 HIGH 0.12.0 0.14.0
org.apache.zookeeper:zookeeper CVE-2023-44981 🔥 CRITICAL 3.6.3 3.7.2, 3.8.3, 3.9.1
org.eclipse.jetty:jetty-server CVE-2024-13009 🚨 HIGH 9.4.56.v20240826 9.4.57.v20241219
org.lz4:lz4-java CVE-2025-12183 🚨 HIGH 1.8.0 1.8.1

🛡️ TRIVY SCAN RESULT 🛡️

Target: Node.js

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Python

Vulnerabilities (9)

Package Vulnerability ID Severity Installed Version Fixed Version
apache-airflow CVE-2025-68438 🚨 HIGH 3.1.5 3.1.6
apache-airflow CVE-2025-68675 🚨 HIGH 3.1.5 3.1.6, 2.11.1
cryptography CVE-2026-26007 🚨 HIGH 42.0.8 46.0.5
jaraco.context CVE-2026-23949 🚨 HIGH 6.0.1 6.1.0
starlette CVE-2025-62727 🚨 HIGH 0.48.0 0.49.1
urllib3 CVE-2025-66418 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2025-66471 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2026-21441 🚨 HIGH 1.26.20 2.6.3
wheel CVE-2026-24049 🚨 HIGH 0.45.1 0.46.2

🛡️ TRIVY SCAN RESULT 🛡️

Target: /etc/ssl/private/ssl-cert-snakeoil.key

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/extended_sample_data.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/lineage.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data.json

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data_aut.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage.json

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage_aut.yaml

No Vulnerabilities Found

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

🛡️ TRIVY SCAN RESULT 🛡️

Target: openmetadata-ingestion:trivy (debian 12.12)

Vulnerabilities (4)

Package Vulnerability ID Severity Installed Version Fixed Version
libpam-modules CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2
libpam-modules-bin CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2
libpam-runtime CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2
libpam0g CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2

🛡️ TRIVY SCAN RESULT 🛡️

Target: Java

Vulnerabilities (38)

Package Vulnerability ID Severity Installed Version Fixed Version
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.12.7 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.12.7 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.13.4 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.13.4 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.15.2 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.16.1 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-databind CVE-2022-42003 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4.2
com.fasterxml.jackson.core:jackson-databind CVE-2022-42004 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4
com.google.code.gson:gson CVE-2022-25647 🚨 HIGH 2.2.4 2.8.9
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.3.0 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.3.0 3.25.5, 4.27.5, 4.28.2
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.7.1 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.7.1 3.25.5, 4.27.5, 4.28.2
com.nimbusds:nimbus-jose-jwt CVE-2023-52428 🚨 HIGH 9.8.1 9.37.2
com.squareup.okhttp3:okhttp CVE-2021-0341 🚨 HIGH 3.12.12 4.9.2
commons-beanutils:commons-beanutils CVE-2025-48734 🚨 HIGH 1.9.4 1.11.0
commons-io:commons-io CVE-2024-47554 🚨 HIGH 2.8.0 2.14.0
dnsjava:dnsjava CVE-2024-25638 🚨 HIGH 2.1.7 3.6.0
io.airlift:aircompressor CVE-2025-67721 🚨 HIGH 0.27 2.0.3
io.netty:netty-codec-http2 CVE-2025-55163 🚨 HIGH 4.1.96.Final 4.2.4.Final, 4.1.124.Final
io.netty:netty-codec-http2 GHSA-xpw8-rcwv-8f8p 🚨 HIGH 4.1.96.Final 4.1.100.Final
io.netty:netty-handler CVE-2025-24970 🚨 HIGH 4.1.96.Final 4.1.118.Final
net.minidev:json-smart CVE-2021-31684 🚨 HIGH 1.3.2 1.3.3, 2.4.4
net.minidev:json-smart CVE-2023-1370 🚨 HIGH 1.3.2 2.4.9
org.apache.avro:avro CVE-2024-47561 🔥 CRITICAL 1.7.7 1.11.4
org.apache.avro:avro CVE-2023-39410 🚨 HIGH 1.7.7 1.11.3
org.apache.derby:derby CVE-2022-46337 🔥 CRITICAL 10.14.2.0 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0
org.apache.ivy:ivy CVE-2022-46751 🚨 HIGH 2.5.1 2.5.2
org.apache.mesos:mesos CVE-2018-1330 🚨 HIGH 1.4.3 1.6.0
org.apache.thrift:libthrift CVE-2019-0205 🚨 HIGH 0.12.0 0.13.0
org.apache.thrift:libthrift CVE-2020-13949 🚨 HIGH 0.12.0 0.14.0
org.apache.zookeeper:zookeeper CVE-2023-44981 🔥 CRITICAL 3.6.3 3.7.2, 3.8.3, 3.9.1
org.eclipse.jetty:jetty-server CVE-2024-13009 🚨 HIGH 9.4.56.v20240826 9.4.57.v20241219
org.lz4:lz4-java CVE-2025-12183 🚨 HIGH 1.8.0 1.8.1

🛡️ TRIVY SCAN RESULT 🛡️

Target: Node.js

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Python

Vulnerabilities (23)

Package Vulnerability ID Severity Installed Version Fixed Version
Authlib CVE-2026-28802 🚨 HIGH 1.6.6 1.6.7
Werkzeug CVE-2024-34069 🚨 HIGH 2.2.3 3.0.3
aiohttp CVE-2025-69223 🚨 HIGH 3.12.12 3.13.3
aiohttp CVE-2025-69223 🚨 HIGH 3.13.2 3.13.3
apache-airflow CVE-2025-68438 🚨 HIGH 3.1.5 3.1.6
apache-airflow CVE-2025-68675 🚨 HIGH 3.1.5 3.1.6, 2.11.1
apache-airflow-providers-http CVE-2025-69219 🚨 HIGH 5.6.0 6.0.0
azure-core CVE-2026-21226 🚨 HIGH 1.37.0 1.38.0
cryptography CVE-2026-26007 🚨 HIGH 42.0.8 46.0.5
google-cloud-aiplatform CVE-2026-2472 🚨 HIGH 1.130.0 1.131.0
google-cloud-aiplatform CVE-2026-2473 🚨 HIGH 1.130.0 1.133.0
jaraco.context CVE-2026-23949 🚨 HIGH 5.3.0 6.1.0
jaraco.context CVE-2026-23949 🚨 HIGH 6.0.1 6.1.0
protobuf CVE-2026-0994 🚨 HIGH 4.25.8 6.33.5, 5.29.6
pyasn1 CVE-2026-23490 🚨 HIGH 0.6.1 0.6.2
python-multipart CVE-2026-24486 🚨 HIGH 0.0.20 0.0.22
ray CVE-2025-62593 🔥 CRITICAL 2.47.1 2.52.0
starlette CVE-2025-62727 🚨 HIGH 0.48.0 0.49.1
urllib3 CVE-2025-66418 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2025-66471 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2026-21441 🚨 HIGH 1.26.20 2.6.3
wheel CVE-2026-24049 🚨 HIGH 0.45.1 0.46.2
wheel CVE-2026-24049 🚨 HIGH 0.45.1 0.46.2

🛡️ TRIVY SCAN RESULT 🛡️

Target: usr/bin/docker

Vulnerabilities (3)

Package Vulnerability ID Severity Installed Version Fixed Version
stdlib CVE-2025-68121 🔥 CRITICAL v1.25.5 1.24.13, 1.25.7, 1.26.0-rc.3
stdlib CVE-2025-61726 🚨 HIGH v1.25.5 1.24.12, 1.25.6
stdlib CVE-2025-61728 🚨 HIGH v1.25.5 1.24.12, 1.25.6

🛡️ TRIVY SCAN RESULT 🛡️

Target: /etc/ssl/private/ssl-cert-snakeoil.key

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /home/airflow/openmetadata-airflow-apis/openmetadata_managed_apis.egg-info/PKG-INFO

No Vulnerabilities Found

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

Jest test Coverage

UI tests summary

Lines Statements Branches Functions
Coverage: 65%
66% (57374/86927) 45.67% (30269/66269) 48.47% (9088/18746)

Copy link
Collaborator

@TeddyCr TeddyCr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments

@gitar-bot
Copy link

gitar-bot bot commented Mar 12, 2026

Code Review ✅ Approved 10 resolved / 10 findings

Adds Informix database connection configuration with comprehensive schema and connection handling. All nine issues were resolved including debug statements, query qualifiers, required field handling, password masking, and capability flags.

✅ 10 resolved
Quality: Debug/development log statement left in production code

📄 ingestion/src/metadata/profiler/orm/functions/table_metric_computer.py:671
Line 671 contains what appears to be a development-time debug marker logged at INFO level with distinctive Unicode markers (◆◆COLLATE-IFX◆◆). This will emit noisy, non-standard log output in production for every Informix table metric computation. It should be removed or, if logging is needed here, downgraded to logger.debug with a conventional message format.

Edge Case: Fallback to super().compute() will always fail on Informix

📄 ingestion/src/metadata/profiler/orm/functions/table_metric_computer.py:697
The except block on line 697 catches any failure in the Informix-specific logic and falls back to super().compute(). However, the entire reason InformixTableMetricComputer exists is that the base implementation uses literal() which places bind parameters (?) in the SELECT clause — something Informix JDBC rejects. So the fallback will always fail with the original SQLSyntaxErrorException, masking the real error that caused the Informix-specific code to fail.

This creates a confusing debugging experience: the actual root cause (e.g. a permissions issue, a network timeout) is logged at debug level and immediately buried by the secondary failure from the base class.

Edge Case: systables query lacks owner/schema qualifier

📄 ingestion/src/metadata/profiler/orm/functions/table_metric_computer.py:724
InformixTableMetricComputer calls self._build_table("systables", None), generating an unqualified FROM systables. Every other metric computer (DB2 uses SYSCAT, MySQL uses information_schema, Postgres uses pg_catalog, etc.) provides an explicit schema. The canonical Informix form is "informix".systables — omitting it relies on default search-path resolution and could fail if the session's default owner doesn't resolve systables. Consider passing "informix" as the schema argument.

Edge Case: Informix database not required but needed for connection

📄 openmetadata-spec/src/main/resources/json/schema/entity/services/connections/database/informixConnection.json:58 📄 openmetadata-spec/src/main/resources/json/schema/entity/services/connections/database/informixConnection.json:145
The informixConnection.json schema marks database as optional, with a description stating it will attempt to scan all databases if left blank. However, the SQLAlchemy connection URL for Informix typically requires a database in the path (informix://user:pass@host:port/database). If no database is provided, the connection URL may be malformed. Verify the Informix ingestion source handles the missing database field gracefully (e.g., by listing and iterating databases).

Bug: Unparsed date proxy leaks through when all strptime formats fail

📄 ingestion/src/metadata/profiler/orm/functions/table_metric_computer.py:759 📄 ingestion/src/metadata/profiler/orm/functions/table_metric_computer.py:766
In table_metric_computer.py lines 759-766, if the JayDeBeApi Java string proxy for created doesn't match any of the three date formats (%Y-%m-%d, %Y-%m-%d %H:%M:%S, %m/%d/%Y), the for loop completes without setting d[CREATE_DATETIME], so it retains the original Java proxy object. Downstream in core.py, this value is treated as a datetime and .replace(tzinfo=timezone.utc) is called on it, which will raise AttributeError since the proxy has no .replace() method.

This is a runtime crash for any Informix instance that returns a date format not covered by the three patterns.

...and 5 more resolved from earlier reviews

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

@sonarqubecloud
Copy link

@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed for 'open-metadata-ingestion'

Failed conditions
1.2% Coverage on New Code (required ≥ 20%)

See analysis details on SonarQube Cloud

@ulixius9 ulixius9 merged commit 00fdb30 into open-metadata:main Mar 13, 2026
38 of 44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Ingestion safe to test Add this label to run secure Github workflows on PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants