Skip to content

chore(deps): opentelemetry 1.67.0 in the Selenium, Appium and Selenide examples - #30

Merged
pashidlos merged 1 commit into
masterfrom
chore/deps-security
Nov 3, 2026
Merged

pashidlos merged 1 commit into
masterfrom
chore/deps-security

Conversation

@pashidlos

Copy link
Copy Markdown
Member

Selenium 4.52.0, Appium java-client 11.0.0 and Selenide 7.19.1 are the latest releases, and they still bring io.opentelemetry:opentelemetry-api 1.66.0 (GHSA-ccrj-gw8r-854m / CVE-2026-118259, quadratic CPU use when parsing W3C tracestate; fixed in 1.67.0). This PR imports opentelemetry-bom 1.67.0 in selenium-maven, appium-maven and selenide-gradle.

Dependabot shows 0 open alerts for this repo because it reads the poms statically and never sees this transitive dependency. I resolved every module (mvn dependency:list -DincludeScope=test, gradle dependencies) and checked all coordinates against OSV:

known vulnerabilities
master 1 (opentelemetry-api 1.66.0)
this PR 0 (84 packages; opentelemetry-api resolves to 1.67.0)

Once Selenium and Selenide ship opentelemetry ≥ 1.67, the BOM pin can go. Dependabot keeps its version current in the meantime.

Can merge now. It's independent of the Java 25 PR, which waits for sdk-java 6.0.

🤖 Generated with Claude Code

…e examples

Selenium 4.52.0 and Selenide 7.19.1, the latest releases, still bring
opentelemetry-api 1.66.0 (CVE-2026-118259). The opentelemetry BOM pins 1.67.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@pashidlos
pashidlos merged commit 2f65011 into master Nov 3, 2026
5 checks passed
@pashidlos
pashidlos deleted the chore/deps-security branch November 3, 2026 06:50
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.

1 participant