Skip to content

flyway-core-9.16.3.jar: 9 vulnerabilities (highest severity is: 8.1) #395

Description

@mend-bolt-for-github
Vulnerable Library - flyway-core-9.16.3.jar

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.15.4/jackson-core-2.15.4.jar

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Vulnerabilities

Vulnerability Severity CVSS Dependency Type Fixed in (flyway-core version) Remediation Possible**
CVE-2026-54513 High 8.1 jackson-databind-2.15.4.jar Transitive N/A*
CVE-2026-54512 High 8.1 jackson-databind-2.15.4.jar Transitive N/A*
WS-2026-0003 High 7.5 jackson-core-2.15.4.jar Transitive 9.17.0
CVE-2026-68494 High 7.5 jackson-core-2.15.4.jar Transitive 9.17.0
CVE-2026-59888 Medium 6.5 jackson-databind-2.15.4.jar Transitive 9.17.0
CVE-2026-54515 Medium 5.3 jackson-databind-2.15.4.jar Transitive N/A*
CVE-2026-54514 Medium 5.3 jackson-databind-2.15.4.jar Transitive N/A*
CVE-2026-18401 Medium 5.3 jackson-core-2.15.4.jar Transitive 9.17.0
CVE-2025-48924 Medium 5.3 commons-lang3-3.12.0.jar Transitive N/A*

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-54513

Vulnerable Library - jackson-databind-2.15.4.jar

General data-binding functionality for Jackson: works on core streaming API

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.15.4/jackson-databind-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray() allowlists any array type based only on clazz.isArray(), without validating the array's component (element) type against the configured allowlist. A PTV built with allowIfSubTypeIsArray() plus an explicit concrete-type allowlist therefore still permits EvilType[] even though EvilType is not allowlisted. When Jackson deserializes the elements and no per-element type IDs are present, it instantiates the component type directly with no further PTV check, bypassing the allowlist. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.

Publish Date: 2026-06-23

URL: CVE-2026-54513

CVSS 3 Score Details (8.1)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: High
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-06-23

Fix Resolution: https://github.com/FasterXML/jackson-databind.git - jackson-databind-3.1.4

Step up your Open Source Security Game with Mend here

CVE-2026-54512

Vulnerable Library - jackson-databind-2.15.4.jar

General data-binding functionality for Jackson: works on core streaming API

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.15.4/jackson-databind-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, jackson-databind's PolymorphicTypeValidator (PTV) is the primary safety mechanism guarding polymorphic deserialization. When polymorphic typing is enabled and a type identifier contains generic parameters (i.e. the type ID string contains <), DatabindContext._resolveAndValidateGeneric() validates only the raw container class name (the substring before <) against the configured PTV. If the container type is approved, the method parses the full canonical type string via TypeFactory.constructFromCanonical() and returns the fully parameterized type without ever validating the nested type arguments against the PTV. The nested type arguments are then resolved, instantiated, and populated as beans during deserialization. An attacker who controls the type ID can therefore place a denied class as a generic type parameter of an allowed container — for example java.util.ArrayList<com.evil.Gadget> when only java.util.ArrayList is allow-listed. The container passes the PTV check; com.evil.Gadget is loaded via Class.forName(name, true, loader), instantiated, and its properties are set from attacker-controlled JSON. This completely bypasses an explicitly configured PTV allow-list. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.

Publish Date: 2026-06-23

URL: CVE-2026-54512

CVSS 3 Score Details (8.1)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: High
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-06-23

Fix Resolution: https://github.com/FasterXML/jackson-databind.git - jackson-databind-2.18.8

Step up your Open Source Security Game with Mend here

WS-2026-0003

Vulnerable Library - jackson-core-2.15.4.jar

Core Jackson processing abstractions (aka Streaming API), implementation for JSON

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.15.4/jackson-core-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar
        • jackson-core-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

The non-blocking (async) JSON parser in jackson-core bypasses the maxNumberLength constraint (default: 1000 characters) defined in StreamReadConstraints. This allows an attacker to send JSON with arbitrarily long numbers through the async parser API, leading to excessive memory allocation and potential CPU exhaustion, resulting in a Denial of Service (DoS).

The standard synchronous parser correctly enforces this limit, but the async parser fails to do so, creating an inconsistent enforcement policy.

Publish Date: 2026-03-02

URL: WS-2026-0003

CVSS 3 Score Details (7.5)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: None
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-72hv-8253-57qq

Release Date: 2026-03-02

Fix Resolution (com.fasterxml.jackson.core:jackson-core): 2.18.6

Direct dependency fix Resolution (org.flywaydb:flyway-core): 9.17.0

Step up your Open Source Security Game with Mend here

CVE-2026-68494

Vulnerable Library - jackson-core-2.15.4.jar

Core Jackson processing abstractions (aka Streaming API), implementation for JSON

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.15.4/jackson-core-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar
        • jackson-core-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 (GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser) is incomplete. This record covers the remaining bypass.
The earlier fix wired validateIntegerLength() into a new _setIntLength() helper and invoked it wherever the integer portion of a number is decided: a terminator byte arrives, a '.' or 'e'/'E' is seen, or input ends inside a fully buffered value. It was not invoked on the attacker-relevant path where the parser runs out of input while still inside the MINOR_NUMBER_INTEGER_DIGITS minor state and returns NOT_AVAILABLE to the caller.
As a result, an attacker who streams JSON to a non-blocking parser in many small chunks, without ever sending a terminator byte, keeps the parser inside MINOR_NUMBER_INTEGER_DIGITS indefinitely. _textBuffer.expandCurrentSegment() grows the accumulator on every chunk while validateIntegerLength() is never called. The accumulator is bounded only by maxStringLength (20 MiB by default) rather than by maxNumberLength (1000 by default), an amplification of roughly 20,000x over the documented limit. Because Java char values occupy two bytes, a single connection can be driven to approximately 40 MiB of heap before the validator finally fires when the value completes.
The equivalent fraction-path code is correct: _finishFloatFraction() calls _setFractLength() before its NOT_AVAILABLE return. The missing call affects the integer-digit paths in _startPositiveNumber(), _startNegativeNumber() and _finishNumberIntegralPart() in NonBlockingUtf8JsonParserBase.
Impact: reactive frameworks such as Spring WebFlux/Reactor, Quarkus, Helidon and Vert.x feed inbound HTTP or gRPC bytes to the async parser as they arrive, which is precisely the chunked-feed shape required. Operators who set StreamReadConstraints.maxNumberLength expecting it to cap memory per number value do not get that guarantee; memory accumulates per concurrent connection and attacker-controlled concurrency can exhaust the JVM heap. The synchronous parsers (UTF8StreamJsonParser, ReaderBasedJsonParser) and the async parser operating on complete input are not affected.
Exploitation requires only the ability to stream data to a parsing endpoint; no privileges or user interaction are needed.
This issue affects com.fasterxml.jackson.core:jackson-core from version 2.15.0 through 2.18.7, and from 2.19.0 through 2.21.3, and tools.jackson.core:jackson-core from 3.0.0 through 3.1.3. 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-r7wm-3cxj-wff9 states the affected 2.x range without a lower bound. The 2.22.x and 3.2.x release lines are not affected: those branches were created after the fix commit landed on 2026-05-21 and therefore contain it from their initial releases (2.22.0, tagged 2026-06-03, and 3.2.0, tagged 2026-06-08).

Publish Date: 2026-08-04

URL: CVE-2026-68494

CVSS 3 Score Details (7.5)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: None
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-08-04

Fix Resolution (com.fasterxml.jackson.core:jackson-core): 2.18.8

Direct dependency fix Resolution (org.flywaydb:flyway-core): 9.17.0

Step up your Open Source Security Game with Mend here

CVE-2026-59888

Vulnerable Library - jackson-databind-2.15.4.jar

General data-binding functionality for Jackson: works on core streaming API

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.15.4/jackson-databind-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.15.0 until 2.18.8, 2.21.4, and 3.1.4, Java Records using a PropertyNamingStrategy can bypass @⁠JsonIgnore because POJOPropertiesCollector._removeUnwantedIgnorals() records an ignored component under its original implicit name before _renameUsing() applies the naming strategy, allowing the renamed JSON key to be assigned to the Record constructor parameter. This issue is fixed in versions 2.18.8, 2.21.4, and 3.1.4.

Publish Date: 2026-07-14

URL: CVE-2026-59888

CVSS 3 Score Details (6.5)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: Low
    • Integrity Impact: Low
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-3pjw-73gf-8qr5

Release Date: 2026-07-14

Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.18.8

Direct dependency fix Resolution (org.flywaydb:flyway-core): 9.17.0

Step up your Open Source Security Game with Mend here

CVE-2026-54515

Vulnerable Library - jackson-databind-2.15.4.jar

General data-binding functionality for Jackson: works on core streaming API

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.15.4/jackson-databind-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.8.0 until 2.18.9, 2.21.5, and 3.1.4, in BeanDeserializerBase.createContextual(), per-property @⁠JsonIgnoreProperties exclusions are applied by _handleByNameInclusion(), producing a contextual deserializer whose BeanPropertyMap has the ignored properties removed. The subsequent per-property case-insensitivity block (triggered by @⁠JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds from this._beanProperties (the original, unfiltered map) instead of contextual._beanProperties, then overwrites the filtered map — restoring every property _handleByNameInclusion had just removed. The ignored property becomes writable again. This vulnerability is fixed in 2.18.9, 2.21.5, and 3.1.4.

Publish Date: 2026-06-23

URL: CVE-2026-54515

CVSS 3 Score Details (5.3)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: Low
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-06-23

Fix Resolution: https://github.com/FasterXML/jackson-databind.git - jackson-databind-3.1.4,com.fasterxml.jackson.core:jackson-databind:2.21.5,com.fasterxml.jackson.core:jackson-databind:2.22.1,https://github.com/FasterXML/jackson-databind.git - jackson-databind-2.18.9,https://github.com/FasterXML/jackson-databind.git - jackson-databind-2.21.5,https://github.com/FasterXML/jackson-databind.git - jackson-databind-2.22.1

Step up your Open Source Security Game with Mend here

CVE-2026-54514

Vulnerable Library - jackson-databind-2.15.4.jar

General data-binding functionality for Jackson: works on core streaming API

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.15.4/jackson-databind-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.4, and 3.1.4, JDKFromStringDeserializer constructed InetSocketAddress with new InetSocketAddress(host, port), which performs eager DNS name resolution for hostname inputs at deserialization time. An application that binds untrusted JSON into a type containing an InetSocketAddress field issues an attacker-chosen DNS query during readValue, before any application-level validation or connect logic. The fix uses InetSocketAddress.createUnresolved(host, port), deferring DNS to an explicit connect. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.

Publish Date: 2026-06-23

URL: CVE-2026-54514

CVSS 3 Score Details (5.3)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: Low
    • Integrity Impact: None
    • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-06-23

Fix Resolution: https://github.com/FasterXML/jackson-databind.git - jackson-databind-2.18.8

Step up your Open Source Security Game with Mend here

CVE-2026-18401

Vulnerable Library - jackson-core-2.15.4.jar

Core Jackson processing abstractions (aka Streaming API), implementation for JSON

Library home page: http://fasterxml.com/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.15.4/jackson-core-2.15.4.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • jackson-dataformat-toml-2.15.4.jar
      • jackson-databind-2.15.4.jar
        • jackson-core-2.15.4.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

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.

Publish Date: 2026-08-04

URL: CVE-2026-18401

CVSS 3 Score Details (5.3)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: None
    • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-08-04

Fix Resolution (com.fasterxml.jackson.core:jackson-core): 2.18.6

Direct dependency fix Resolution (org.flywaydb:flyway-core): 9.17.0

Step up your Open Source Security Game with Mend here

CVE-2025-48924

Vulnerable Library - commons-lang3-3.12.0.jar

Apache Commons Lang, a package of Java utility classes for the classes that are in java.lang's hierarchy, or are considered to be so standard as to justify existence in java.lang.

Library home page: https://www.apache.org/

Sample Path to Dependency File: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar

Dependency Hierarchy:

  • flyway-core-9.16.3.jar (Root Library)
    • commons-text-1.10.0.jar
      • commons-lang3-3.12.0.jar (Vulnerable Library)

Found in HEAD commit: 985d4a71b0cc06b07e4e37fda7739bbfc0dfc733

Found in base branch: master

Vulnerability Details

Uncontrolled Recursion vulnerability in Apache Commons Lang.
This issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.
The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a
StackOverflowError could cause an application to stop.
Users are recommended to upgrade to version 3.18.0, which fixes the issue.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2025-07-11

URL: CVE-2025-48924

CVSS 3 Score Details (5.3)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • Integrity Impact: None
    • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2025-07-11

Fix Resolution: https://github.com/apache/commons-lang.git - commons-lang-3.18.0,org.apache.commons:commons-lang3:3.18.0

Step up your Open Source Security Game with Mend here

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions