The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2025-968 advisory.

    The net/http package accepted data in the chunked transfer encoding containing an invalid chunk-size line     terminated by a bare LF. When used in conjunction with a server or proxy which incorrectly interprets a     bare LF in a chunk extension as part of the extension, this could permit request smuggling.
    (CVE-2025-22871)

    Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr     expression parser is given an unbounded input string, it will attempt to compile the entire string and     generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size     isn't limited, a malicious or inadvertent extremely large expression can consume excessive memory as the     parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM)     crash of the process. This issue is relatively uncommon and will only manifest when there are no     restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In     typical use cases where inputs are bounded or validated, this problem would not occur. The problem has     been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the     number of AST nodes and memory usage during parsing, preventing any single expression from exhausting     resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node     budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions     are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot     immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In     practice, this means validating or limiting the length of expression strings that your application will     accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject     or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the     parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory     exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.
    (CVE-2025-29786)

    golang-jwt is a Go implementation of JSON Web Tokens. Prior to5.2.2 and 4.5.2, the function     parse.ParseUnverified splits (via a call to strings.Split) its argument (which is untrusted data) on     periods. As a result, in the face of a malicious request whose Authorization header consists of Bearer     followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes     (where n stands for the length of the function's argument), with a constant factor of about 16. This issue     is fixed in 5.2.2 and 4.5.2. (CVE-2025-30204)

Tenable has extracted the preceding description block directly from the tested product 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 version of amazon-cloudwatch-agent installed on the remote host is prior to 1.300054.1-2. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2025-2851 advisory.

    The net/http package accepted data in the chunked transfer encoding containing an invalid chunk-size line     terminated by a bare LF. When used in conjunction with a server or proxy which incorrectly interprets a     bare LF in a chunk extension as part of the extension, this could permit request smuggling.
    (CVE-2025-22871)

    Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr     expression parser is given an unbounded input string, it will attempt to compile the entire string and     generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size     isn't limited, a malicious or inadvertent extremely large expression can consume excessive memory as the     parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM)     crash of the process. This issue is relatively uncommon and will only manifest when there are no     restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In     typical use cases where inputs are bounded or validated, this problem would not occur. The problem has     been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the     number of AST nodes and memory usage during parsing, preventing any single expression from exhausting     resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node     budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions     are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot     immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In     practice, this means validating or limiting the length of expression strings that your application will     accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject     or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the     parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory     exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.
    (CVE-2025-29786)

    golang-jwt is a Go implementation of JSON Web Tokens. Prior to5.2.2 and 4.5.2, the function     parse.ParseUnverified splits (via a call to strings.Split) its argument (which is untrusted data) on     periods. As a result, in the face of a malicious request whose Authorization header consists of Bearer     followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes     (where n stands for the length of the function's argument), with a constant factor of about 16. This issue     is fixed in 5.2.2 and 4.5.2. (CVE-2025-30204)

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

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

According to the versions of the golang packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines.
    This can permit request smuggling if a net/http server is used in conjunction with a server that     incorrectly accepts a bare LF as part of a chunk-ext.(CVE-2025-22871)

Tenable has extracted the preceding description block directly from the EulerOS golang 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 Fedora 40 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2025-f974cb8ce5 advisory.

    Includes security fixes to the net/http package, as well as bug fixes to the runtime and the go command.
    [Full changelog](https://github.com/golang/go/issues?q=milestone%3AGo1.23.8+label%3ACherryPickApproved).

Tenable has extracted the preceding description block directly from the Fedora 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 version of golang / msft-golang installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2025-22871 advisory.

  - The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines.
    This can permit request smuggling if a net/http server is used in conjunction with a server that     incorrectly accepts a bare LF as part of a chunk-ext. (CVE-2025-22871)

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 golang installed on the remote host is prior to 1.23.8-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2-2025-2825 advisory.

    The net/http package accepted data in the chunked transfer encoding containing an invalid chunk-size line     terminated by a bare LF. When used in conjunction with a server or proxy which incorrectly interprets a     bare LF in a chunk extension as part of the extension, this could permit request smuggling.
    (CVE-2025-22871)

Tenable has extracted the preceding description block directly from the tested product 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 Fedora 41 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2025-77ace1a41b advisory.

    Includes security fixes to the net/http package, as well as bug fixes to the runtime and the go command.
    [Full changelog](https://github.com/golang/go/issues?q=milestone%3AGo1.23.8+label%3ACherryPickApproved).

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

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

It is, therefore, affected by a vulnerability as referenced in the ALAS2023-2025-933 advisory.

    The net/http package accepted data in the chunked transfer encoding containing an invalid chunk-size line     terminated by a bare LF. When used in conjunction with a server or proxy which incorrectly interprets a     bare LF in a chunk extension as part of the extension, this could permit request smuggling.
    (CVE-2025-22871)

Tenable has extracted the preceding description block directly from the tested product 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 SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:1153-1 advisory.

    - Update to go1.24.2
    - CVE-2025-22871: Fix an issue with request smuggling through invalid chunked data. (bsc#1240550)

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 SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:1141-1 advisory.

    - Update to go1.23.8
    - CVE-2025-22871: Fix an issue with request smuggling through invalid chunked data. (bsc#1240550)

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 Golang running on the remote host is 1.24 prior to 1.24.2. It is, therefore, is affected by multiple vulnerabilities:

  - Unlike request headers, where we are allowed to leniently accept a bare LF in place of a CRLF,     chunked bodies must always use CRLF line terminators. We were already enforcing this for chunk-data lines;
    do so for chunk-size lines as well. Also reject bare CRs anywhere other than as part of the CRLF terminator.

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	Severity
235902	Amazon Linux 2023 : amazon-cloudwatch-agent (ALAS2023-2025-968)	Nessus	Amazon Linux Local Security Checks	high
235886	Amazon Linux 2 : amazon-cloudwatch-agent (ALAS-2025-2851)	Nessus	Amazon Linux Local Security Checks	high
235766	EulerOS 2.0 SP10 : golang (EulerOS-SA-2025-1516)	Nessus	Huawei Local Security Checks	critical
235765	EulerOS 2.0 SP10 : golang (EulerOS-SA-2025-1517)	Nessus	Huawei Local Security Checks	critical
234731	Fedora 40 : golang (2025-f974cb8ce5)	Nessus	Fedora Local Security Checks	critical
234633	CBL Mariner 2.0 Security Update: golang / msft-golang (CVE-2025-22871)	Nessus	MarinerOS Local Security Checks	critical
234512	Amazon Linux 2 : golang (ALAS-2025-2825)	Nessus	Amazon Linux Local Security Checks	critical
234461	Fedora 41 : golang (2025-77ace1a41b)	Nessus	Fedora Local Security Checks	medium
234340	Amazon Linux 2023 : golang, golang-bin, golang-misc (ALAS2023-2025-933)	Nessus	Amazon Linux Local Security Checks	critical
233984	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : go1.24 (SUSE-SU-2025:1153-1)	Nessus	SuSE Local Security Checks	critical
233887	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : go1.23 (SUSE-SU-2025:1141-1)	Nessus	SuSE Local Security Checks	critical
233871	Golang 1.24 < 1.24.2	Nessus	Windows	high

Detections

Analytics

CVE-2025-22871

critical

Tenable Plugins

high

high

critical

critical

critical

critical

critical

medium

critical

critical

critical

high