Skip to main content
Components
Vulnerabilities
Security Events
Pricing
MCP
API
Docs
Sign up
Login
Find vulnerabilities. Fix fast with AI.
Search components by package, version, or CVE to get started.
io.github.vishalmysore/a2a-mcp-security 0.… | Sonatype Guide
Get full component data and automated fixes with Sonatype Guide.
Sign up for free
maven
io.github.vishalmysore
a2a-mcp-security
0.0.1
a2a-mcp-security 0.0.1
Latest
io.github.vishalmysore
Published
May 23, 2025
•
Policy
compliance
maven Registry
Developer Trust Score
Recommended Version:
x.y.z
Recommended upgrade that meets your policy.
Compare Versions
Overview
Overview
Versions
1
Versions
1
Vulnerabilities
340
Vulnerabilities
340
Dependencies
27
Dependencies
27
Reset filters
Severity
Critical
(0)
High
(0)
Medium
(131)
Low
(0)
CVSS Score
0.0
10.0
EPSS Score
0.0
1.0
Malware
KEV Status
Published
Filter
Sort: Published (Newest first)
5.9
CVE-2026-59419
Spring Framework - Denial of Service via HTTP client observations
affected
Severity
Medium
Published
Nov 20, 2026
5.6
CVE-2026-59430
Spring Framework - SpEL expression injection via type conversion bypass
affected
Severity
Medium
Published
Nov 20, 2026
5.9
CVE-2026-59391
Spring Framework - STOMP message authorization bypass vulnerability
affected
Severity
Medium
Published
Nov 20, 2026
6.9
CVE-2026-59431
Spring Framework - SpEL expression DoS via collection selection
affected
Severity
Medium
Published
Nov 20, 2026
5.3
CVE-2026-59389
Spring Framework - Multipart request smuggling vulnerability
affected
Severity
Medium
Published
Nov 20, 2026
4.2
CVE-2026-59373
Spring Boot - Jedis SSL auto-configuration does not enable TLS hostname verification
affected
Severity
Medium
Published
Nov 20, 2026
5.7
CVE-2026-59392
Spring Framework - STOMP message disclosure via SockJS transport
affected
Severity
Medium
Published
Nov 20, 2026
5.9
CVE-2026-59418
Spring Framework - Denial of service via streaming text decoding in WebFlux
affected
Severity
Medium
Published
Nov 20, 2026
5.3
CVE-2026-59398
Spring Framework - Denial of Service via Parameter-based Content Negotiation
affected
Severity
Medium
Published
Nov 20, 2026
6.3
CVE-2026-129482
OkHttp through 5.5.1 contains an improper certificate validation vulnerability in CertificatePinner that skips pin checks because Pin.matchesHostname does not normalize trailing-dot hostnames. Network attackers with a CA-trusted certificate not matching configured pins can intercept or modify TLS traffic when applications request the trailing-dot form of pinned hosts.
affected
Severity
Medium
Published
Nov 16, 2026
6.3
CVE-2026-103615
org.bouncycastle:bcpkix - Improper Validation of Consistency within Input
affected
Severity
Medium
Published
Nov 13, 2026
6.3
CVE-2026-103613
org.bouncycastle:bcprov - Incomplete Cleanup
affected
Severity
Medium
Published
Nov 13, 2026
6.9
CVE-2026-103611
org.bouncycastle:bcprov - Inefficient Algorithmic Complexity
affected
Severity
Medium
Published
Nov 13, 2026
6.9
CVE-2026-103610
org.bouncycastle:bcpkix - Inefficient Algorithmic Complexity
affected
Severity
Medium
Published
Nov 13, 2026
6.3
CVE-2026-103606
org.bouncycastle:bcpkix - Use of Weak Hash
affected
Severity
Medium
Published
Nov 13, 2026
5.3
sonatype-2026-011018
org.javassist:javassist - Improper Resource Shutdown or Release
affected
Severity
Medium
Published
Nov 13, 2026
6.9
CVE-2026-119078
Apache Commons Codec's Blake3 class documented the output of its doFinalize methods as depending on any previously finalized bytes, so that consecutive calls would return different output. In fact, doFinalize does not change the hash state: calling it again without supplying more input returns the same bytes. The key-derivation example in the class Javadoc, shipped since 1.16.0, derives two keys with two consecutive doFinalize calls. Code that follows it gets identical keys, so the separation between the derived keys is lost. The same applies to any application that calls doFinalize more than once on one instance and expects new output each time. This issue affects Apache Commons Codec from 1.16.0 before 1.23.0. Version 1.23.0 corrects the documentation, but the behavior of doFinalize is unchanged. Upgrading alone does not fix affected code. Users should check their applications for repeated doFinalize calls on the same Blake3 instance and derive multiple keys by requesting the combined length in one call and splitting the output, as the updated Javadoc shows.
affected
Severity
Medium
Published
Nov 10, 2026
4.0
sonatype-2026-009989
org.apache.commons:commons-lang3 - Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
affected
Severity
Medium
Published
Oct 28, 2026
6.3
CVE-2026-88041
Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer information from a previous request to leak into a subsequent request. This issue affects Apache Tomcat: from 11.0.0-M23 through 11.0.26, from 10.1.27 through 10.1.60, from 9.0.92 through 9.0.122. Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.
affected
Severity
Medium
Published
Oct 21, 2026
6.9
CVE-2026-18401
The non-blocking (asynchronous) JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints (default: 1000 characters). An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length, leading to excessive memory allocation and potential CPU exhaustion, resulting in a denial of service. The synchronous parser enforces this limit correctly, so the constraint is applied inconsistently depending on which parsing API the application uses. Root cause: the async parsing path in NonBlockingUtf8JsonParserBase and related classes never invokes the number length validation methods. Number parsing methods such as _finishNumberIntegralPart() accumulate digits into the TextBuffer without any length check, then call _valueComplete() to finalize the token. _valueComplete() does not call resetInt() or resetFloat(), which are the methods in ParserBase where validateIntegerLength() and validateFPLength() are performed. Because that validation step is skipped, maxNumberLength is never enforced on the async code path. Impact: an attacker sending a JSON document containing an arbitrarily long number to an application using the async parser (for example a Spring WebFlux or other reactive application) can cause unbounded allocation in the TextBuffer and an OutOfMemoryError. If the application subsequently calls getBigIntegerValue() or getDecimalValue(), the JVM may additionally be tied up in O(n^2) BigInteger parsing, causing CPU-based denial of service. No privileges or user interaction beyond the ability to submit data for parsing are required. This issue affects com.fasterxml.jackson.core:jackson-core from version 2.15.0 through 2.18.5 and from 2.19.0 through 2.21.0, and tools.jackson.core:jackson-core from 3.0.0 through 3.0.x. Versions prior to 2.15.0 are not affected, because StreamReadConstraints -- which defines the maxNumberLength setting -- was first introduced in jackson-core 2.15.0, so no such constraint exists to be bypassed in earlier releases. Note that GHSA-72hv-8253-57qq records the lower bound of the affected 2.x range as 2.0.0.
affected
Severity
Medium
Published
Oct 15, 2026
5.3
sonatype-2026-009330
OpenTelemetry Java - Regex backtracking causes DoS in tracestate parsing
affected
Severity
Medium
Published
Oct 15, 2026
6.3
CVE-2026-104721
Path-traversal vulnerability in QOS.CH Sarl Logback-classic on Java (logback-classic module) allows path-traversal vulnerability. More specifically, an MDC-based discriminator value flows unsanitized into a nested FileAppender path, letting an attacker who influences that MDC value (e.g. via an HTTP header) create and append log files outside the intended directory. This issue affects Logback-classic: from 0.9.14 through 1.6.4. This vulnerability is similar to CVE-2026-19880 but involves other attack techniques.
affected
Severity
Medium
Published
Oct 5, 2026
5.3
CVE-2026-97873
In Bouncy Castle for Java before 1.86, the raw JCA provider's legacy PBES1 (PKCS#5 scheme 1) and PKCS#12 PBE families ran their password-based key derivation with an iteration count taken from untrusted input without bounding it, so a small input could dictate an arbitrary amount of work before anything could be verified. The AlgorithmParameters implementations (PKCS12PBE and its object identifier aliases, and PBKDF1) accepted any count from an encoded PKCS12PBEParams or PBEParameter, narrowing a value beyond the int range with intValue(), and every Cipher, Mac and SecretKeyFactory in these families derived with whatever count it was given, including one decoded by another provider's AlgorithmParameters, as when javax.crypto.EncryptedPrivateKeyInfo.getKeySpec() decrypts a PKCS#12 PBE-protected private key with BC. Both the parameter parse and the derivations now reject a negative or over-limit count under the org.bouncycastle.pbe.max_iteration_count property (default 10,000,000) that already bounded PBKDF2 (CVE-2026-17508), and the parse rejects a count beyond the int range rather than narrowing it. This issue also affects Bouncy Castle for Java LTS before 2.73.13.
affected
Severity
Medium
Published
Oct 3, 2026
6.3
CVE-2026-73581
Improper Check for Certificate Revocation vulnerability in Apache Tomcat. Both the OpenSSL and OpenSSL-FFM TLS implementations ignore CRLs when certificate uses a keystore. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.25, from 10.1.0-M1 through 10.1.59, from 9.0.0-M1 through 9.0.121. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.26, 10.1.59, 9.0.122, which fixes the issue.
affected
Severity
Medium
Published
Sep 24, 2026
6.3
CVE-2026-77756
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in Apache Tomcat caused by processing the transfer-encoding header for an HTTP/1.0 request may allow an attacker to cause one request from another user to fail when Tomcat is located behind a reverse proxy. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.25, from 10.1.0-M1 through 10.1.59, from 9.0.47 through 9.0.121. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.67 through 8.5.100. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.26, 10.1.60 or 9.0.122, which fix the issue.
affected
Severity
Medium
Published
Sep 24, 2026
1-25 of 131