chore(findings): opensource/apache-pulsar/pulsar-latest
Summary
opensource/apache-pulsar/pulsar-latest has 1 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/apache-pulsar/pulsar-latest&tag=4.0.6&branch=master
EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.
KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.
id | source | severity | package | impact | workaround | epss_score | kev |
---|---|---|---|---|---|---|---|
CVE-2025-58056 | Twistlock CVE | High | io.netty_netty-codec-http-4.1.122.Final | N/A | false |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/apache-pulsar/pulsar-latest&tag=4.0.6&branch=master
Novel Tidelift Findings (Experimental)
opensource/apache-pulsar/pulsar-latest has 7 novel Tidelift findings discovered during continuous monitoring.
NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.
id | cvss score | package | impact | workaround | epss_score | kev |
---|---|---|---|---|---|---|
CVE-2025-48924 | 6.5 | commons-lang:commons-lang-2.6 | 0.00309 | false | ||
CVE-2024-31033 | 6.8 | io.jsonwebtoken:jjwt-impl-0.11.1 | 0.00131 | false | ||
CVE-2024-6763 | 3.7 | org.eclipse.jetty:jetty-http-9.4.57.v20241219 | If using the Jetty internal HttpURI as part of Jetty server and Jetty client you are not vulnerable.If using HttpURI in your application directly, then you are vulnerable if you use the results of HttpURI to apply filtering based on the given URI. | 0.00090 | false | |
CVE-2025-8916 | 6.3 | org.bouncycastle:bcpkix-jdk18on-1.78.1 | 0.00055 | false | ||
CVE-2025-55163 | 8.2 | io.netty:netty-codec-http2-4.1.122.Final | Although this vulnerability is legit, it is relatively hard to exploit this vulnerability to cause actual server instability, because modern hardware will not spend much resources to handle bogus RSTSTREAM frames. | A user can attach an Http2FrameListener implementation that disconnects a client that sends too many RSTSTREAM or any other invalid frames in a certain amount of time. | 0.00055 | false |
CVE-2025-58057 | 6.9 | io.netty:netty-codec-4.1.122.Final | N/A | false | ||
CVE-2025-58056 | 8.2 | io.netty:netty-codec-http-4.1.122.Final | N/A | false |
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
Verification
label will be removed and the issue will be sent back toOpen
. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theVerification
label.
Questions?
Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding
.
Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.