Amazon Linux 2027 Preview Security Advisory: ALAS2027-2026-345
Advisory Released Date: 2026-11-12
Advisory Updated Date: 2026-11-13
FAQs regarding Amazon Linux ALAS/CVE Severity
OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. Prior to 4.0.0, the client_credentials and Resource Owner Password Credentials token grant handlers can authenticate request.client as one confidential client while retaining an attacker-supplied request.client_id for validate_grant_type and validate_scopes. A lower-privilege authenticated client can therefore cause grant and scope authorization to use another client's identity when an application validator relies on the documented client_id argument, potentially issuing tokens with unauthorized grants or scopes. Validators that authorize exclusively from request.client may not be affected. This issue is fixed in version 4.0.0. (CVE-2026-118669)
A flaw was found in oauthlib. When JSON with Padding (JSONP) support is enabled on the token revocation endpoint, the application fails to validate user-supplied callback parameters before reflecting them into the response. A remote attacker could exploit this flaw by submitting a crafted callback value, allowing the execution of arbitrary JavaScript code within the security context of client applications consuming the response. (CVE-2026-49264)
A flaw was found in oauthlib. A timing side-channel vulnerability in the Proof Key for Code Exchange (PKCE) validation process allows a remote attacker to recover secret verification codes. Because comparison operations do not execute in constant time, an attacker who has intercepted an authorization code can measure response latency differences across repeated requests to infer the expected verification code character-by-character. Successful exploitation allows the attacker to exchange the authorization code for an access token and impersonate the victim user. (CVE-2026-49265)
OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. From 3.3.0 until 4.0.1, OAuthLib's RFC 8628 device workflow does not require DeviceCodeGrant.validate_token_request to check that the device_code parameter is present and valid. A caller whose client request is accepted by the configured validator and who knows a valid client ID enabled for the device workflow can submit a missing or bogus device code to the token endpoint and obtain a bearer token without completing device authorization. This issue is fixed in version 4.0.1. (CVE-2026-49272)
Affected Packages:
python-oauthlib
Issue Correction:
Run dnf update python-oauthlib --releasever 2027.0.20261112 or dnf update --advisory ALAS2027-2026-345 --releasever 2027.0.20261112 to update your system.
More information on how to update your system can be found on this page: Amazon Linux 2027 documentation
noarch:
python3-oauthlib+signals-4.0.1-1.amzn2027.0.1.noarch
python3-oauthlib+rsa-4.0.1-1.amzn2027.0.1.noarch
python3-oauthlib+signedtoken-4.0.1-1.amzn2027.0.1.noarch
python3-oauthlib-4.0.1-1.amzn2027.0.1.noarch
src:
python-oauthlib-4.0.1-1.amzn2027.0.1.src