Skip to content

build(autoconf): restrict supported Python versions to <3.14#987

Merged
AlessandroPomponio merged 1 commit into
mainfrom
ap_20260602_update_autoconf
Jun 2, 2026
Merged

build(autoconf): restrict supported Python versions to <3.14#987
AlessandroPomponio merged 1 commit into
mainfrom
ap_20260602_update_autoconf

Conversation

@AlessandroPomponio
Copy link
Copy Markdown
Member

Related to #969

Signed-off-by: Alessandro Pomponio <alessandro.pomponio1@ibm.com>
@DRL-NextGen
Copy link
Copy Markdown
Member

Checks Summary

Last run: 2026-06-02T08:18:41.444Z

Mend Unified Agent vulnerability scan found 2 vulnerabilities:

Severity Identifier Package Details Fix
🔷 Medium CVE-2026-48710 starlette-0.52.1-py3-none-any.whl
Starlette is a lightweight ASGI framework/toolkit. Prior to version 1.0.1, the HTTP "Host" request h...Starlette is a lightweight ASGI framework/toolkit. Prior to version 1.0.1, the HTTP "Host" request header was not validated before being used to reconstruct "request.url". Because the routing algorithm relies on the raw HTTP path while "request.url" is rebuilt from the "Host" header, a malformed header could make "request.url.path" differ from the path that was actually requested. Middleware and endpoints that apply security restrictions based on "request.url" (rather than the raw "scope" path) could therefore be bypassed. Users should upgrade to a version greater than or equal to version 1.0.1, which validates the "Host" header against the grammar of RFC 9112 §3.2 / RFC 3986 §3.2.2 when constructing "request.url" and falls back to "scope["server"]" for malformed values.
Upgrade to version starlette - 1.0.1,starlette - 1.0.1,https://github.com/Kludex/starlette.git - 1.0.1
🔷 Medium CVE-2026-45409 idna-3.14-py3-none-any.whl
This is the same issue as CVE-2024-3651, however the original remediation in 2024 was not a complete...This is the same issue as CVE-2024-3651, however the original remediation in 2024 was not a complete fix. Payloads such as ""\u0660" * N" or ""\u30fb" * N + "\u6f22"" utilize the "valid_contexto" function prior to length rejection, and for high values of "N" will take a long time to process. Impact A specially crafted argument to the "idna.encode()" function could consume significant resources. This may lead to a denial-of-service. Patches Starting in version 3.14, the function rejects long inputs as soon as practicable prior to any further processing to minimize resource consumption. In version 3.15, this approach was extended to lesser used alternate functions (i.e. per-label conversions and codec support). Workarounds Domain names cannot exceed 253 characters in length, if this length limit is enforced prior to passing the domain to the "idna.encode()" function it should no longer consume significant resources. This is triggered by arbitrarily large inputs that would not occur in normal usage, but may be passed to the library assuming there is no preliminary input validation by the higher-level application.
Upgrade to version idna - 3.15

AlessandroPomponio added a commit that referenced this pull request Jun 2, 2026
Changes will be done in #987

Signed-off-by: Alessandro Pomponio <alessandro.pomponio1@ibm.com>
@AlessandroPomponio AlessandroPomponio added this pull request to the merge queue Jun 2, 2026
Merged via the queue into main with commit 5bc63c7 Jun 2, 2026
18 checks passed
@AlessandroPomponio AlessandroPomponio deleted the ap_20260602_update_autoconf branch June 2, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants