A possible security vulnerability has been identified in Apache Kafka. This requires access to a alterConfig to the cluster resource, or Kafka Connect worker, and the ability to create/modify connectors on it with an arbitrary Kafka client SASL JAAS config and a SASL-based security protocol, which has been possible on Kafka clusters since Apache Kafka 2.0.0 (Kafka Connect 2.3.0). When configuring the broker via config file or AlterConfig command, or connector via the Kafka Kafka Connect REST API, an authenticated operator can set the `sasl.jaas.config` property for any of the connector's Kafka clients to "com.sun.security.auth.module.LdapLoginModule", which can be done via the `producer.override.sasl.jaas.config`, `consumer.override.sasl.jaas.config`, or `admin.override.sasl.jaas.config` properties. This will allow the server to connect to the attacker's LDAP server and deserialize the LDAP response, which the attacker can use to execute java deserialization gadget chains on the Kafka connect server. Attacker can cause unrestricted deserialization of untrusted data (or) RCE vulnerability when there are gadgets in the classpath. Since Apache Kafka 3.0.0, users are allowed to specify these properties in connector configurations for Kafka Connect clusters running with out-of-the-box configurations. Before Apache Kafka 3.0.0, users may not specify these properties unless the Kafka Connect cluster has been reconfigured with a connector client override policy that permits them. Since Apache Kafka 3.9.1/4.0.0, we have added a system property ("-Dorg.apache.kafka.disallowed.login.modules") to disable the problematic login modules usage in SASL JAAS configuration. Also by default "com.sun.security.auth.module.JndiLoginModule,com.sun.security.auth.module.LdapLoginModule" are disabled in Apache Kafka Connect 3.9.1/4.0.0. We advise the Kafka users to validate connector configurations and only allow trusted LDAP configurations. Also examine connector dependencies for vulnerable versions and either upgrade their connectors, upgrading that specific dependency, or removing the connectors as options for remediation. Finally, in addition to leveraging the "org.apache.kafka.disallowed.login.modules" system property, Kafka Connect users can also implement their own connector client config override policy, which can be used to control which Kafka client properties can be overridden directly in a connector config and which cannot.

An update of the kafka package has been released.

The versions of Oracle Siebel CRM installed on the remote host are affected by multiple vulnerabilities as referenced in the April 2026 CPU advisory.

  - Vulnerability in the Siebel CRM Integration product of Oracle Siebel CRM (component: REST (Jettison)).
    Supported versions that are affected are 17.0-26.2. Easily exploitable vulnerability allows     unauthenticated attacker with network access via HTTP to compromise Siebel CRM Integration. Successful     attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable     crash (complete DOS) of Siebel CRM Integration. (CVE-2022-40149, CVE-2022-40150, CVE-2022-45685,     CVE-2022-45693, CVE-2023-1436, CVE-2026-28493, CVE-2026-28494, CVE-2026-28686, CVE-2026-28687,     CVE-2026-28688, CVE-2026-28689, CVE-2026-28690, CVE-2026-28691, CVE-2026-28692, CVE-2026-28693,     CVE-2026-30883, CVE-2026-30929, CVE-2026-30931, CVE-2026-30935, CVE-2026-30936)

  - Vulnerability in the Siebel CRM Deployment product of Oracle Siebel CRM (component: Keyword Automation     (Netty)). Supported versions that are affected are 17.0-26.2. Easily exploitable vulnerability allows     unauthenticated attacker with network access via HTTP to compromise Siebel CRM Deployment. Successful     attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable     crash (complete DOS) of Siebel CRM Deployment. (CVE-2025-58056, CVE-2025-58057)

  - Vulnerability in the Siebel CRM Integration product of Oracle Siebel CRM (component: Event Publish and     Subscribe (Apache Kafka)). Supported versions that are affected are 17.0-26.2. Easily exploitable     vulnerability allows unauthenticated attacker with network access via TCP to compromise Siebel CRM     Integration. Successful attacks of this vulnerability can result in unauthorized access to critical data     or complete access to all Siebel CRM Integration accessible data. (CVE-2025-27817, CVE-2025-27818)

  - Vulnerability in the Siebel CRM Integration product of Oracle Siebel CRM (component: Event Publish and     Subscribe (jose4j)). Supported versions that are affected are 17.0-26.2. Easily exploitable vulnerability     allows unauthenticated attacker with network access via HTTP to compromise Siebel CRM Integration.
    Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently     repeatable crash (complete DOS) of Siebel CRM Integration. (CVE-2023-51775, CVE-2024-29371)

  - Vulnerability in the Siebel CRM Deployment product of Oracle Siebel CRM (component: Keyword Automation     (Apache Commons Lang)). Supported versions that are affected are 17.0-26.2. Easily exploitable     vulnerability allows unauthenticated attacker with network access via HTTP to compromise Siebel CRM     Deployment. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial     denial of service (partial DOS) of Siebel CRM Deployment. (CVE-2025-48924)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - A possible security vulnerability has been identified in Apache Kafka. This requires access to a
    alterConfig to the cluster resource, or Kafka Connect worker, and the ability to create/modify connectors
    on it with an arbitrary Kafka client SASL JAAS config and a SASL-based security protocol, which has been
    possible on Kafka clusters since Apache Kafka 2.0.0 (Kafka Connect 2.3.0). When configuring the broker via
    config file or AlterConfig command, or connector via the Kafka Kafka Connect REST API, an authenticated
    operator can set the `sasl.jaas.config` property for any of the connector's Kafka clients to
    "com.sun.security.auth.module.LdapLoginModule", which can be done via the
    `producer.override.sasl.jaas.config`, `consumer.override.sasl.jaas.config`, or
    `admin.override.sasl.jaas.config` properties. This will allow the server to connect to the attacker's LDAP
    server and deserialize the LDAP response, which the attacker can use to execute java deserialization
    gadget chains on the Kafka connect server. Attacker can cause unrestricted deserialization of untrusted
    data (or) RCE vulnerability when there are gadgets in the classpath. Since Apache Kafka 3.0.0, users are
    allowed to specify these properties in connector configurations for Kafka Connect clusters running with
    out-of-the-box configurations. Before Apache Kafka 3.0.0, users may not specify these properties unless
    the Kafka Connect cluster has been reconfigured with a connector client override policy that permits them.
    Since Apache Kafka 3.9.1/4.0.0, we have added a system property
    ("-Dorg.apache.kafka.disallowed.login.modules") to disable the problematic login modules usage in SASL
    JAAS configuration. Also by default
    "com.sun.security.auth.module.JndiLoginModule,com.sun.security.auth.module.LdapLoginModule" are disabled
    in Apache Kafka Connect 3.9.1/4.0.0. We advise the Kafka users to validate connector configurations and
    only allow trusted LDAP configurations. Also examine connector dependencies for vulnerable versions and
    either upgrade their connectors, upgrading that specific dependency, or removing the connectors as options
    for remediation. Finally, in addition to leveraging the "org.apache.kafka.disallowed.login.modules" system
    property, Kafka Connect users can also implement their own connector client config override policy, which
    can be used to control which Kafka client properties can be overridden directly in a connector config and
    which cannot. (CVE-2025-27818)

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0475 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2025-27818:
    A possible security vulnerability has been identified in Apache Kafka.
    This requires access to a alterConfig to thecluster resource, or Kafka Connect worker, and the ability     to create/modify connectors on it with an arbitrary Kafka client SASL JAAS config     and a SASL-based security protocol, which has been possible on Kafka clusters since Apache Kafka 2.0.0     (Kafka Connect 2.3.0).
    When configuring the broker via config file or AlterConfig command, or connector via the Kafka Kafka     Connect REST API, an authenticated operatorcan set the `sasl.jaas.config`     property for any of the connector's Kafka clients to com.sun.security.auth.module.LdapLoginModule, which     can be done via the     `producer.override.sasl.jaas.config`, `consumer.override.sasl.jaas.config`, or     `admin.override.sasl.jaas.config` properties.
    This will allow the server to connect to the attacker's LDAP server     and deserialize the LDAP response, which the attacker can use to execute java deserialization gadget     chains on the Kafka connect server.
    Attacker can cause unrestricted deserialization of untrusted data (or) RCE vulnerability when there are     gadgets in the classpath.

    Since Apache Kafka 3.0.0, users are allowed to specify these properties in connector configurations for     Kafka Connect clusters running with out-of-the-box     configurations. Before Apache Kafka 3.0.0, users may not specify these properties unless the Kafka Connect     cluster has been reconfigured with a connector     client override policy that permits them.

    Since Apache Kafka 3.9.1/4.0.0, we have added a system property     (-Dorg.apache.kafka.disallowed.login.modules) to disable the problematic login modules usage     in SASL JAAS configuration. Also by default     com.sun.security.auth.module.JndiLoginModule,com.sun.security.auth.module.LdapLoginModule are disabled     in Apache Kafka Connect 3.9.1/4.0.0.

    We advise the Kafka users to validate connector configurations and only allow trusted LDAP configurations.
    Also examine connector dependencies for     vulnerable versions and either upgrade their connectors, upgrading that specific dependency, or removing     the connectors as options for remediation. Finally,     in addition to leveraging the org.apache.kafka.disallowed.login.modules system property, Kafka Connect     users can also implement their own connector     client config override policy, which can be used to control which Kafka client properties can be     overridden directly in a connector config and which cannot.

    CVE-2025-27817:
    A possible arbitrary file read and SSRF vulnerability has been identified in Apache Kafka Client. Apache     Kafka Clients accept configuration data for setting the SASL/OAUTHBEARER connection with the brokers,     including sasl.oauthbearer.token.endpoint.url and sasl.oauthbearer.jwks.endpoint.url. Apache Kafka     allows clients to read an arbitrary file and return the content in the error log, or sending requests to     an unintended location. In applications where Apache Kafka Clients configurations can be specified by an     untrusted party, attackers may use the sasl.oauthbearer.token.endpoint.url and     sasl.oauthbearer.jwks.endpoint.url configuratin to read arbitrary contents of the disk and environment     variables or make requests to an unintended location. In particular, this flaw may be used in Apache Kafka     Connect to escalate from REST API access to filesystem/environment/URL access, which may be undesirable in     certain environments, including SaaS products.

    Since Apache Kafka 3.9.1/4.0.0, we have added a system property     (-Dorg.apache.kafka.sasl.oauthbearer.allowed.urls) to set the allowed urls in SASL JAAS configuration.
    In 3.9.1, it accepts all urls by default for backward compatibility. However in 4.0.0 and newer, the     default value is empty list and users have to set the allowed urls explicitly.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
333721	Photon OS 5.0: Kafka PHSA-2025-5.0-91-0537	Nessus	PhotonOS Local Security Checks	Local	high
309923	Oracle Siebel Server <= 26.2 (April 2026 CPU)	Nessus	Misc.	Local	high
436365	SCA: security update for org.apache.kafka:kafka_2.12, org.apache.kafka:kafka_2.13 (GHSA-76qp-h5mr-frr4)	Tenable Cloud Security	SCA Checks	Local	high
436365	SCA: security update for org.apache.kafka:kafka_2.12, org.apache.kafka:kafka_2.13 (GHSA-76qp-h5mr-frr4)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
276292	TencentOS Server 4: kafka (TSSA-2025:0475)	Nessus	Tencent Local Security Checks	Local	high
242402	Photon OS 4.0: Kafka PHSA-2025-4.0-0834	Nessus	PhotonOS Local Security Checks	Local	high
240414	Photon OS 5.0: Kafka PHSA-2025-5.0-0537	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2025-27818

high

Tenable Plugins

high

high

high

high

high

high

high