Skip to content
VulniPulse
Medium 2 vendors · 2 advisories

CVE-2026-105930: Apache Pulsar: When package management is enabled, Pulsar Functions, Sources and Sinks can be registered or updated from a package stored in the Pulsar Packages Management Service by supplying a package URL

CVE-2026-105930 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
6.5 (Red Hat), 6 (Apache)
Weakness
CWE-639
Fixed releases
  • Apache: 4.0.14, 4.2.5
  • Red Hat: 4.0.14, 4.2.5
Vendor advisories
2 from Apache, Red Hat
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-105930; each belongs to its advisory, not to every product listed. How records are collected and checked.

How do I fix CVE-2026-105930?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.0.14, 4.2.5
  • Red Hat: 4.0.14, 4.2.5
  • An authenticated user who is permitted to register or update functions, sources or sinks in any namespace of their own tenant could use this to obtain the contents of a package stored in a namespace of another tenant, without having the packages permission on that namespace. (Apache)
  • This issue affects Apache Pulsar versions from 2.8.0 before 4.0.14, from 4.1.0 through 4.1.3, and from 4.2.0 before 4.2.5. - 4.0.x version users should upgrade to at least 4.0.14. - 4.1.x and 4.2.x version users should upgrade to at least 4.2.5. (Apache)

Vendor advisories for CVE-2026-105930

Apache

1 advisory
  • Advisory severityMedium6.0

    Medium [CVE-2026-105930] Apache Pulsar: When package management is enabled, Pulsar Functions, Sources and Sinks can be registered or updated from a package stored in the Pulsar Packages Management Service by supplying a package URL

    CVE-2026-105930Source published Source updated

    When package management is enabled, Pulsar Functions, Sources and Sinks can be registered or updated from a package stored in the Pulsar Packages Management Service by supplying a package URL. The Pulsar Functions worker authorized these requests only against the namespace in which the component was being registered or updated. It did not check whether the requesting user was permitted to access packages in the namespace that the package URL refers to, and it retrieved the package from the broker using the worker's own credentials. The permission check of the Packages Management Service was therefore applied to the worker's identity instead of the requesting user's. Package URLs of transform functions supplied when registering or updating a sink were handled in the same way. An…

    Affected products in this advisory
    • Apache Pulsar
    Source-reported affected versions
    • 4.1.0 through 4.1.3
    • 2.8.0 before 4.0.14
    • 4.2.0 before 4.2.5
    Source-reported fixed versions
    • 4.0.14
    • 4.2.5
    Mitigation guidance
    • An authenticated user who is permitted to register or update functions, sources or sinks in any namespace of their own tenant could use this to obtain the contents of a package stored in a namespace of another tenant, without having the packages permission on that namespace.
    • This issue affects Apache Pulsar versions from 2.8.0 before 4.0.14, from 4.1.0 through 4.1.3, and from 4.2.0 before 4.2.5. - 4.0.x version users should upgrade to at least 4.0.14. - 4.1.x and 4.2.x version users should upgrade to at least 4.2.5.
    • Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.

Red Hat

1 advisory

References

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery