gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2026:1194-1 advisory.

    This update for google-cloud-sap-agent fixes the following issue:

    Update to google-cloud-sap-agent 3.12 (bsc#1259816):

    - CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2:
    path pseudo-       header (bsc#1260265).

    Changelog:

     * Collect WLM metric `saphanasr_angi_installed` for all OS types.
     * Failure handling: Remove attached disks from CG
     * OTE Status checks for Parameter Manager (SAP Agent)
     * Log command-line arguments in configureinstance.
     * Minor multiple reliability checks and fixes
     * Support custom names for restored disks in hanadiskrestore
     * Add newAttachedDisks to Restorer and detach them on restore failure.
     * Improve unit test coverage for hanadiskbackup and hanadiskrestore
     * Add support for refresh point tests.
     * Refactor HANA disk backup user validation and physical path parsing.
     * Auto updated compiled protocol buffers
     * Parameter Manager integration to SAP Agent
     * Modify collection logic for SAP HANA configuration files.
     * Update workloadagentplatform version and hash.
     * Update WLM Validation metrics to support SAPHanaSR-angi setups.
     * Increment agent version to 3.12.
     * SAP HANA Pacemaker failover settings can come from `SAPHanaController`.
     * Update collection for WLM metric `ha_sr_hook_configured`.
     * Refactor CheckTopology to accept instance number.
     * Use constant backoff with max retries for snapshot group operations.
     * Update workloadagentplatform dependency

Tenable has extracted the preceding description block directly from the SUSE 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 remote SUSE Linux SLES12 / SLES_SAP12 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2026:1195-1 advisory.

    This update for google-cloud-sap-agent fixes the following issue:

    Update to google-cloud-sap-agent 3.12 (bsc#1259816):

    - CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2:
    path pseudo-       header (bsc#1260265).

    Changelog:

     * Collect WLM metric `saphanasr_angi_installed` for all OS types.
     * Failure handling: Remove attached disks from CG
     * OTE Status checks for Parameter Manager (SAP Agent)
     * Log command-line arguments in configureinstance.
     * Minor multiple reliability checks and fixes
     * Support custom names for restored disks in hanadiskrestore
     * Add newAttachedDisks to Restorer and detach them on restore failure.
     * Improve unit test coverage for hanadiskbackup and hanadiskrestore
     * Add support for refresh point tests.
     * Refactor HANA disk backup user validation and physical path parsing.
     * Auto updated compiled protocol buffers
     * Parameter Manager integration to SAP Agent
     * Modify collection logic for SAP HANA configuration files.
     * Update workloadagentplatform version and hash.
     * Update WLM Validation metrics to support SAPHanaSR-angi setups.
     * Increment agent version to 3.12.
     * SAP HANA Pacemaker failover settings can come from `SAPHanaController`.
     * Update collection for WLM metric `ha_sr_hook_configured`.
     * Refactor CheckTopology to accept instance number.
     * Use constant backoff with max retries for snapshot group operations.
     * Update workloadagentplatform dependency

Tenable has extracted the preceding description block directly from the SUSE 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 FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 09e36f7e-2b5b-11f1-852e-5404a68ad561 advisory.

    The traefik project releases a new version addressing multiple CVEs:

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

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

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass     resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too     lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash     (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests     to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated     the raw, non-canonical path string. Consequently, deny rules defined using canonical paths (starting     with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback allow     rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the     official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on     `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific deny rules     for canonical paths but allows other requests by default (a fallback allow rule). The vulnerability is     exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the     gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a     leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching     authorization interceptors or handlers with a non-canonical path string. While upgrading is the most     secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use     a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy     hardening. (CVE-2026-33186)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
305288	SUSE SLES15 / openSUSE 15 Security Update : google-cloud-sap-agent (SUSE-SU-2026:1194-1)	Nessus	SuSE Local Security Checks	critical
305287	SUSE SLES12 Security Update : google-cloud-sap-agent (SUSE-SU-2026:1195-1)	Nessus	SuSE Local Security Checks	critical
304263	FreeBSD : traefik -- Multiple vulnerabilities (09e36f7e-2b5b-11f1-852e-5404a68ad561)	Nessus	FreeBSD Local Security Checks	medium
303458	Linux Distros Unpatched Vulnerability : CVE-2026-33186	Nessus	Misc.	critical

Detections

Analytics

CVE-2026-33186

critical

Tenable Plugins

critical

critical

medium

critical