Update MongoDB version

[mchiefsauce]

Update MongoDB to 8.2.3 to fix CVE-2025-14847
(not exploitable directly since doesn't have ingress route)

Summary by CodeRabbit

• Chores
  • Updated MongoDB to patch version 8.2.3 to maintain infrastructure stability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

MongoDB Helm chart image tag updated from version 8.2.2 to 8.2.3 in the values configuration file. No functional or logic changes present.

Changes

Cohort / File(s)	Summary
MongoDB Helm Chart Configuration infra/mongodb/values.yaml	Image tag bumped from 8.2.2 to 8.2.3 for MongoDB container

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version hops along the way,
Eight-point-two-point-three today!
MongoDB fresh, prepared to run,
The upgrade dance has just begun. 🚀

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update MongoDB version' directly reflects the main change in the changeset - updating the MongoDB image tag from 8.2.2 to 8.2.3.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a1a4686 and 72ee7b1.

📒 Files selected for processing (1)

• infra/mongodb/values.yaml

🔇 Additional comments (1)

infra/mongodb/values.yaml (1)

3-3: Update is appropriate—CVE-2025-14847 is real and MongoDB 8.2.3 addresses it.

CVE-2025-14847 ("MongoBleed") is a confirmed high-severity unauthenticated memory-disclosure vulnerability (CVSS 8.7) in MongoDB's zlib compression handling. MongoDB 8.2.3, released December 19, 2025, specifically fixes this issue and is the latest release in the 8.2 line.

The version bump from 8.2.2 to 8.2.3 is correct. Note that while the vulnerability is unauthenticated (no credentials required), exploitation requires network access to MongoDB. The claim that it is "not directly exploitable due to no ingress route" is valid only if network isolation is confirmed—validate that MongoDB is not exposed to untrusted networks.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Brutus5000]

Merged dependabot PR as it was faster to rebase.