Comparison Using Wrong Factors Affecting openshift4/ose-coredns-rhel9 package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.39% (31st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-OPENSHIFT4OSECOREDNSRHEL9-17099508
  • published30 May 2026
  • disclosed5 May 2026

Introduced: 5 May 2026

CVE-2026-33489  (opens in a new tab)
CWE-1025  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 openshift4/ose-coredns-rhel9.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openshift4/ose-coredns-rhel9 package and not the openshift4/ose-coredns-rhel9 package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the transfer plugin can select the wrong ACL stanza when both a parent zone and a more-specific subzone are configured. The longestMatch() function in plugin/transfer/transfer.go uses a lexicographic string comparison instead of an actual longest-suffix match to select the winning zone. As a result, a permissive parent-zone transfer rule can override a restrictive subzone rule depending on zone name ordering (e.g., "example.org." > "a.example.org." lexicographically). This allows an unauthorized remote client to perform AXFR/IXFR for the subzone and retrieve its full zone contents. This issue has been fixed in version 1.14.3.

CVSS Base Scores

version 3.1