A race condition in AbstractOAuthDataProvider allows concurrent requests using the same Refresh Token to bypass single-use semantics and generate multiple valid Access Tokens, when 'recycleRefreshTokens' is set to false. A leaked refresh token can be replayed concurrently by multiple attackers or threads. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.

The version of AOS installed on the remote host is prior to 7.6.0.6. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AOS-7.6.0.6 advisory.

  - In an untrusted JMS environment, org.springframework.jms.support.converter.MappingJackson2MessageConverter     and org.springframework.jms.support.converter.JacksonJsonMessageConverter allow arbitrary class     instantiation, which can lead to unauthorized actions via gadget class deserialization. Affected versions:
    Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
    (CVE-2026-41855)

  - Postfix before 3.8.16, 3.9 before 3.9.10, and 3.10 before 3.10.9 sometimes allows a buffer over-read and     process crash via an enhanced status code that lacks text after the third number. (CVE-2026-43964)

  - Improper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j     API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through     2.25.4 and version 2.26.0. The fix for CVE-2026-34481 did not cover all code paths: when a MapMessage     contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity), MapMessage.asJson() emits the     corresponding bare token. RFC 8259 does not permit these tokens, so a conformant parser rejects the     resulting document. The defect is reachable only when both of the following conditions hold: * The     application uses the message resolver https://logging.apache.org/log4j/2.x/manual/json-template-     layout.html#event-template-resolver-message of JsonTemplateLayout or any other layout that relies on     MapMessage.asJson() or MapMessage.getFormattedMessage(new String[]{JSON}). * The application logs a     MapMessage that contains an attacker-controlled floating-point value. An attacker who can supply a non-     finite value can cause the affected layout to emit malformed JSON, which may corrupt the enclosing log     record or disrupt downstream log ingestion and parsing. Users are advised to upgrade to Apache Log4j API     2.25.5 or 2.26.1, both of which emit RFC 8259-compliant JSON for non-finite values. (CVE-2026-49844)

  - An authentication bypass vulnerability exists in the OAuth2 TokenIntrospectionService in Apache CXF. Due     to a missing 'throw' keyword in the security context check, the introspection endpoint     (/services/oauth2/introspect) can be accessed by any unauthenticated network attacker. However note that     this is a safeguard only in the case that someone forgot to enable authentication on the service. Users     are recommended to upgrade to version 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue. (CVE-2026-50623)

  - The 'clientId' parameter from incoming HTTP requests is directly concatenated into OAuth2 server log     warning messages without sanitizing control characters. This allows an attacker to inject arbitrary     content, including fake log entries, into the server's log files. Users are recommended to upgrade to     versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue. (CVE-2026-50629)

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 race condition in AbstractOAuthDataProvider allows concurrent requests using the same Refresh Token to
    bypass single-use semantics and generate multiple valid Access Tokens, when 'recycleRefreshTokens' is set
    to false. A leaked refresh token can be replayed concurrently by multiple attackers or threads. Users are
    recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue. (CVE-2026-50631)

The version of Apache CXF installed on the remote host is prior to 4.1.7 or 4.2.x prior to 4.2.2. It is, therefore, affected by multiple vulnerabilities, including:

  - A JNDI Injection vulnerability in the JCA integration module allows code execution if an     attacker can manipulate the JCA deployment descriptor or runtime activation parameters.
    (CVE-2026-50633)

  - An incomplete fix for CVE-2026-44417 allows code execution if untrusted users are allowed to     configure JMS for Apache CXF. (CVE-2026-50632)

  - No restriction on the amount of attachment headers in a message during deserialization can lead     to uncontrolled resource consumption or denial of service. (CVE-2026-50645)

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
341612	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-7.6.0.6)	Nessus	Misc.	Local	high
446179	SCA: security update for org.apache.cxf:cxf-rt-rs-security-oauth2 (GHSA-83r6-96m8-r52p)	Tenable Cloud Security	SCA Checks	Local	high
446179	SCA: security update for org.apache.cxf:cxf-rt-rs-security-oauth2 (GHSA-83r6-96m8-r52p)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
321189	Apache CXF < 4.1.7 / 4.2.x < 4.2.2 Multiple Vulnerabilities	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-50631

high

Tenable Plugins

high

high

high

high