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)

遠端主機上安裝的 Oracle Siebel CRM 版本受到 2026 年 4 月 CPU 公告中所提及的多個弱點影響。

  - Oracle Siebel CRM 的 Siebel CRM Integration 產品中存有弱點 (元件REST (Jettison))。
    受影響的支援版本是 17.0-26.2。可輕鬆惡意利用的弱點允許具有網路存取權的未經驗證的攻擊者透過 HTTP 來危害 Siebel CRM Integration。若成功攻擊此弱點可能導致 Siebel CRM Integration 未經授權即可造成懸置或經常重複性當機 (完全 DOS)。 (CVE-2022-40149, CVE-2022-40150, CVE-2022-45685, CVE-2022-45693, CVE-2023-1436, CVE-2026-28493, CVE-2026-28494CVE-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)

  - Oracle Siebel CRM 的 Siebel CRM Deployment 產品中的弱點 (元件Keyword Automation (Netty))。受影響的支援版本是 17.0-26.2。可輕鬆惡意利用的弱點允許具有網路存取權的未經驗證的攻擊者透過 HTTP 來危害 Siebel CRM Deployment。若成功攻擊此弱點可能導致 Siebel CRM Deployment 未經授權即可造成懸置或經常重複性當機 (完全 DOS)。 (CVE-2025-58056、 CVE-2025-58057)

  - Oracle Siebel CRM 中 Siebel CRM Integration 產品的弱點 (元件Event Publish and Subscribe (Apache kafka))。受影響的支援版本是 17.0-26.2。可輕鬆惡意利用的弱點允許具有網路存取權的未經驗證的攻擊者透過 TCP 來危害 Siebel CRM Integration。成功攻擊此弱點可導致未經授權地存取重要資料或完整存取所有 Siebel CRM Integration 可存取資料。 (CVE-2025-27817、 CVE-2025-27818)

  - Oracle Siebel CRM 的 Siebel CRM Integration 產品中存有一個弱點 (元件Event Publish and Subscribe (jose4j))。受影響的支援版本是 17.0-26.2。可輕鬆惡意利用的弱點允許具有網路存取權的未經驗證的攻擊者透過 HTTP 來危害 Siebel CRM Integration。
    若成功攻擊此弱點可能導致 Siebel CRM Integration 未經授權即可造成懸置或經常重複性當機 (完全 DOS)。 (CVE-2023-51775、 CVE-2024-29371)

  - Oracle Siebel CRM 的 Siebel CRM Deployment 產品中的弱點 (元件Keyword Automation (Apache Commons Lang))。受影響的支援版本是 17.0-26.2。可輕鬆惡意利用的弱點允許具有網路存取權的未經驗證的攻擊者透過 HTTP 來危害 Siebel CRM Deployment。成功攻擊此弱點可導致未經授權即可造成 Siebel CRM Deployment 部分拒絕服務 (部分 DOS)。 (CVE-2025-48924)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

远程主机上安装的 Oracle Siebel CRM 版本受到 2026 年 4 月 CPU 公告中提及的多个漏洞的影响。

  - Oracle Siebel CRM 的 Siebel CRM Integration 产品中的漏洞组件REST (Jettison)。
    支持的版本中受影响的是 17.0-26.2。轻松利用的漏洞允许具有网络访问权限的未经身份验证的攻击者通过 HTTP 危害 Siebel CRM 集成。成功攻击此漏洞可导致在未经授权的情况下使 Siebel CRM Integration 挂起或频繁出现崩溃完整 DOS。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

  - Oracle Siebel CRM 的 Siebel CRM Deployment 产品中的漏洞组件Keyword Automation (Netty)。支持的版本中受影响的是 17.0-26.2。可轻松利用的漏洞允许具有网络访问权限的未经身份验证的攻击者通过 HTTP 破坏 Siebel CRM Deployment。成功攻击此漏洞可导致在未经授权的情况下使 Siebel CRM Deployment 挂起或频繁出现崩溃完整 DOS。CVE-2025-58056、 CVE-2025-58057

  - Oracle Siebel CRM 的 Siebel CRM Integration 产品中的漏洞组件事件发布与订阅 (Apache kafka)。支持的版本中受影响的是 17.0-26.2。可轻松利用的漏洞允许具备网络访问权限的未经身份验证的攻击者通过 TCP 危害 Siebel CRM 集成。成功攻击此漏洞可导致在未经授权的情况下访问重要数据或完整访问所有 Siebel CRM 集成可访问数据。CVE-2025-27817、 CVE-2025-27818

  - Oracle Siebel CRM 的 Siebel CRM Integration 产品中的漏洞组件事件发布与订阅 (jose4j)。支持的版本中受影响的是 17.0-26.2。轻松利用的漏洞允许具有网络访问权限的未经身份验证的攻击者通过 HTTP 危害 Siebel CRM 集成。
    成功攻击此漏洞可导致在未经授权的情况下使 Siebel CRM Integration 挂起或频繁出现崩溃完整 DOS。CVE-2023-51775、 CVE-2024-29371

  - Oracle Siebel CRM 的 Siebel CRM Deployment 产品中的漏洞组件Keyword Automation (Apache Commons Lang)。支持的版本中受影响的是 17.0-26.2。可轻松利用的漏洞允许具有网络访问权限的未经身份验证的攻击者通过 HTTP 破坏 Siebel CRM Deployment。成功攻击此漏洞可导致在未经授权的情况下造成 Siebel CRM Deployment 部分拒绝服务部分 DOS。 (CVE-2025-48924)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

リモートホストにインストールされている Oracle Siebel CRM のバージョンは、2026 年 4 月 CPU アドバイザリで言及されているように、複数の脆弱性の影響を受けます。

  - Oracle Siebel CRMのSiebel CRM Integration製品の脆弱性コンポーネントRESTJettison。
    サポートされているバージョンで影響を受けるのは、17.0-26.2 です。容易に悪用できる脆弱性により、ネットワークアクセス権を持つ認証されていない攻撃者が、HTTPを介してSiebel CRM Integrationを侵害する可能性があります。この脆弱性に対する攻撃が成功すると、権限なくSiebel CRM Integrationをハングさせたり、頻繁にクラッシュを繰り返させたりする可能性完全なDOSがあります。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​

  - Oracle Siebel CRMのSiebel CRM Deployment製品での脆弱性コンポーネントKeyword AutomationNetty。サポートされているバージョンで影響を受けるのは、17.0-26.2 です。容易に悪用できる脆弱性により、ネットワークアクセス権を持つ認証されていない攻撃者が、HTTPを介してSiebel CRM Deploymentを侵害する可能性があります。この脆弱性に対する攻撃が成功すると、権限なくSiebel CRM Deploymentをハングさせたり、頻繁にクラッシュを繰り返させたりする可能性完全なDOSがあります。CVE-2025-58056、 CVE-2025-58057

  - Oracle Siebel CRM の Siebel CRM Integration 製品の脆弱性コンポーネントEvent Publish and SubscribeApache Kafka サポートされているバージョンで影響を受けるのは、17.0-26.2 です。容易に悪用できる脆弱性により、ネットワークアクセス権を持つ認証されていない攻撃者が、TCP経由でSiebel CRM Integrationを侵害する可能性があります。この脆弱性に対する攻撃が成功すると、重要なデータに不正にアクセスしたり、Siebel CRM Integrationでアクセスできるすべてのデータに完全にアクセスしたりできる可能性があります。CVE-2025-27817、 CVE-2025-27818

  - Oracle Siebel CRM の Siebel CRM Integration 製品の脆弱性コンポーネントEvent Publish and Subscribejose4j。サポートされているバージョンで影響を受けるのは、17.0-26.2 です。容易に悪用できる脆弱性により、ネットワークアクセス権を持つ認証されていない攻撃者が、HTTPを介してSiebel CRM Integrationを侵害する可能性があります。
    この脆弱性に対する攻撃が成功すると、権限なくSiebel CRM Integrationをハングさせたり、頻繁にクラッシュを繰り返させたりする可能性完全なDOSがあります。CVE-2023-51775、 CVE-2024-29371

  - Oracle Siebel CRM の Siebel CRM Deployment 製品での脆弱性コンポーネントKeyword AutomationApache Commons Lang。サポートされているバージョンで影響を受けるのは、17.0-26.2 です。容易に悪用できる脆弱性により、ネットワークアクセス権を持つ認証されていない攻撃者が、HTTPを介してSiebel CRM Deploymentを侵害する可能性があります。この脆弱性に対する攻撃が成功すると、権限なくSiebel CRM Deploymentの部分的なサービス拒否部分的DOSが引き起こされる可能性があります。CVE-2025-48924

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

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.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-150467 advisory.

    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.

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

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

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.

An update of the kafka package has been released.

ID	名稱	產品	系列	已發布	已更新	嚴重性
465209	Echo: org.apache.kafka:kafka_2.13: security update to 3.9.1	Tenable Cloud Security	Echo Local Security Checks	2026/10/2	2026/10/5	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	2025/12/12	2026/7/2	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	2025/12/12	2026/7/2	high
465209	Echo: org.apache.kafka:kafka_2.13: security update to 3.9.1	Tenable Self-Hosted Container Security	Echo Local Security Checks	2026/10/2	2026/10/5	high
309923	Oracle Siebel Server <= 26.2 (2026 年 4 月 CPU)	Nessus	Misc.	2026/4/23	2026/4/27	high
309923	Oracle Siebel Server <= 26.2 2026 年 4 月 CPU	Nessus	Misc.	2026/4/23	2026/4/27	high
309923	Oracle Siebel Server <= 26.2 2026 年 4 月 CPU	Nessus	Misc.	2026/4/23	2026/4/27	high
309923	Oracle Siebel Server <= 26.2 (April 2026 CPU)	Nessus	Misc.	2026/4/23	2026/4/27	high
376558	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kafka (UTSA-2026-150467)	Nessus	Unity Linux Local Security Checks	2026/11/5	2026/11/5	high
276292	TencentOS Server 4: kafka (TSSA-2025:0475)	Nessus	Tencent Local Security Checks	2025/11/20	2025/12/4	high
240414	Photon OS 5.0: Kafka PHSA-2025-5.0-0537	Nessus	PhotonOS Local Security Checks	2025/6/25	2026/10/14	high
333721	Photon OS 5.0: Kafka PHSA-2025-5.0-91-0537	Nessus	PhotonOS Local Security Checks	2026/8/10	2026/11/2	high
242402	Photon OS 4.0: Kafka PHSA-2025-4.0-0834	Nessus	PhotonOS Local Security Checks	2025/7/19	2026/11/2	high

偵測

搜尋 Plugin

high

high

high

high

high

high

high

high

high

high

high

high

high