Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Upgrade to amqp-client 5.33.0 in 4.1.x (CVE-2026-63337)

Open Beginner friendly
#52,296 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
backend, security

Research direction

Start with the managed dependency declaration in platform/spring-boot-dependencies/build.gradle and check how dependency versions are recorded nearby. Update the amqp-client version to 5.33.0, then verify the 4.1.x dependency metadata reflects that version.

Written by the indexing model from the issue text.

Description

status: waiting-for-triage

The 4.1.x line currently manages com.rabbitmq:amqp-client 5.30.0 (library("Rabbit AMQP Client", "5.30.0") in platform/spring-boot-dependencies/build.gradle), which is in the affected range of CVE-2026-63337:

  • Unsafe reflection (CWE-470) in com.rabbitmq.tools.jsonrpc.JsonRpcClient: a javaReturnType value from an untrusted system.describe response is passed to Class.forName(...) with initialization enabled
  • Affects amqp-client ≥ 1.3.0 and < 5.33.0; fixed in 5.33.0
  • CVSS v3 base score: 9.0

An attacker who can control broker responses (shared broker or network MITM) could trigger static initializers of classes already present in the victim JVM and cause type confusion.

Would you consider upgrading the managed amqp-client version to 5.33.0 in the 4.1.x branch? 5.33.0 stays on the 5.x line and is compatible with Spring AMQP 4.1.x / Spring Rabbit, so the upgrade should be a drop-in version bump.

Mend vulnerability database entry: https://www.mend.io/vulnerability-database/CVE-2026-63337/

Dominant language
Java
Stars
81.7k
Forks
45.1k
Avg merge
3d 13h
Merged PRs (30d)
58

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-projects/spring-boot

All issues in spring-projects/spring-boot

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.