-
Notifications
You must be signed in to change notification settings - Fork 13
Expand file tree
/
Copy pathrequirements.txt
More file actions
45 lines (45 loc) · 2.53 KB
/
Copy pathrequirements.txt
File metadata and controls
45 lines (45 loc) · 2.53 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
aiohttp>=3.13.3,<4
fastapi>=0.115.6,<1
Jinja2>=3.1.2,<4
pydantic[email]>=1.9.1,<2
requests>=2.32.4,<3
urllib3>=2.6.3,<3
gunicorn>=23.0.0,<24
tenacity>=8.0.1,<9
typer>=0.4.1,<1
uvicorn[standard]>=0.17.6,<1
logzio-python-handler
# ddtrace is capped <4 by opal-common 0.9.6 (`ddtrace<4,>=3.0.0`). CVE-2026-50271 (remote
# DoS via unbounded W3C baggage header extraction) is fixed only in ddtrace >= 4.8.2, so
# it cannot be upgraded away while OPAL holds that cap. Mitigated in the Dockerfile by
# dropping "baggage" from DD_TRACE_PROPAGATION_STYLE_EXTRACT, and waived in
# .docker/scout/pdp-v2.vex.json as not_affected / inline_mitigations_already_exist.
# Pinned exactly so the waiver PURL (pkg:pypi/ddtrace@3.19.8) stays bound - the image
# build has no lockfile, so an unpinned ddtrace would drift to a new 3.x and silently
# break the match. Remove this pin + the waiver + the Dockerfile ENV and upgrade
# ddtrace>=4.8.2 once OPAL relaxes its ddtrace<4 bound. See PER-15358.
ddtrace==3.19.8
# sqlparse is not imported anywhere in the codebase - it has only ever been carried as a
# floor pin from past vulnerability sweeps (see f837d77). Bumped to 0.5.5 to clear
# GHSA-27jp-wm6q-gp25 (fixed in 0.5.4). Candidate for outright removal - tracked separately.
sqlparse==0.5.5
scalar-fastapi==1.0.3
httpx>=0.27.0,<1
# TODO: change to use re2 in the future, currently not supported in alpine due to c++ library issues
# google-re2 # use re2 instead of re for regex matching because it's simiplier and safer for user inputted regexes
protobuf>=6.33.5 # pinned to avoid CVE-2026-0994
cryptography>=48.0.1,<49 # pinned to avoid GHSA-537c-gmf6-5ccf (and CVE-2026-26007)
# starlette is capped <1 by opal-common/opal-client 0.9.6 (and further to <0.51.0 via
# fastapi-utils -> fastapi 0.125.0). Four starlette CVEs (CVE-2026-54283 fixed in 1.3.1,
# CVE-2026-48817 fixed in 1.1.0, CVE-2026-48818 fixed in 1.1.0, CVE-2026-48710 fixed in
# 1.0.1) have no <1 backport, so they cannot be upgraded away while OPAL caps
# starlette<1. All four are waived in .docker/scout/pdp-v2.vex.json as not_affected
# (unreachable code paths: JSON-only API with no request.form(); Linux with no
# StaticFiles; no HTTPEndpoint subclasses; no security decision reads request.url).
# Pinned exactly so the waiver PURLs stay bound (the image build has no lockfile, so an
# unpinned starlette could drift to a new 0.x and silently break the match). Remove this
# pin + all four waivers and upgrade starlette>=1.3.1 once OPAL relaxes its starlette<1
# bound. See PER-15358.
starlette==0.50.0
opal-common==0.9.6
opal-client==0.9.6