You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for migrating ini4j to GitHub and for merging the CVE-2022-41404 fix (#10), good to see the project active again.
A request from a downstream consumer: would you consider publishing an interim, security-only release (e.g. 0.5.5) containing just dda3743, ahead of the full v0.6.0 scope?
0.5.4 (2015) is still the only artifact on Maven Central, and OSV / Trivy / GitHub Advisory all flag it for CVE-2022-41404 (CVSS 7.5). Because the fix is merged but unreleased, downstreams currently have to vendor a locally-patched jar to pass security scanners. An interim 0.5.5 with only the security fix would let everyone drop those patches right away, while v0.6.0’s documentation work (Phase 3) continues on its own timeline. OSSRH access for org.ini4j is already verified per this issue, so it should be low-effort.
Happy to help test a release candidate. Thanks again for picking this up.
Activity
feat(java): modernize POM and resolve Java 17 compatibility (BREAKING) (
tswern commentedon Nov 10, 2026
Thanks for migrating ini4j to GitHub and for merging the CVE-2022-41404 fix (#10), good to see the project active again.
A request from a downstream consumer: would you consider publishing an interim, security-only release (e.g. 0.5.5) containing just dda3743, ahead of the full v0.6.0 scope?
0.5.4 (2015) is still the only artifact on Maven Central, and OSV / Trivy / GitHub Advisory all flag it for CVE-2022-41404 (CVSS 7.5). Because the fix is merged but unreleased, downstreams currently have to vendor a locally-patched jar to pass security scanners. An interim 0.5.5 with only the security fix would let everyone drop those patches right away, while v0.6.0’s documentation work (Phase 3) continues on its own timeline. OSSRH access for org.ini4j is already verified per this issue, so it should be low-effort.
Happy to help test a release candidate. Thanks again for picking this up.