boruta (Hex)

Advisories

Latest version

—

License

—

OpenSSF Scorecard

—

How to fix

Upgrading to 2.3.7 or later clears every advisory below that has a fix.

Upgrade commands

mix

{:boruta, "~> 2.3.7"} # then: mix deps.update boruta

Known vulnerabilities

Advisory	Severity	Affected	Fixed in
EEF-CVE-2026-53431 Boruta accepts expired JWT client assertions due to missing exp claim validation	Not rated yet EPSS 0.51%	`>= 2.3.0, < 2.3.7`	`2.3.7`
EEF-CVE-2026-65635 Boruta dynamic client registration allows creation of over-privileged OAuth clients	Not rated yet EPSS 0.38%	`>= 2.3.0, < 2.3.7`	`2.3.7`
EEF-CVE-2026-54885 Server-side request forgery in Boruta OAuth request_uri and OpenID jwks_uri fetching	Not rated yet EPSS 0.47%	`>= 2.3.2, < 2.3.7`	`2.3.7`

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor