Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Question]: Guidance on jackson-coreutils vulnerabilities in legacy Swagger compatibility dependency

Aperta
#2,405 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Refactoring
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
java

Direzione di ricerca

The problem is the transitive chain swagger-parser-v2-converter → swagger-compat-spec-parser:1.0.71 → json-schema-validator / json-patch → jackson-coreutils:2.0, which is needed only for the Swagger 1.2 path (NoClassDefFoundError on com.github.fge.jackson.jsonpointer.JsonPointer). Done would need a maintainer decision on whether to keep, replace or drop Swagger 1.2 support, so this is not a starting point for a first contribution.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Question

We use `io.swagger.parser.v3:swagger-parser:2.1.23` in a Java 8 application.

The application must currently retain support for parsing legacy Swagger 1.2 documents, in addition to Swagger 2.0 and OpenAPI 3 documents.

Our resolved dependency tree shows that Swagger 1.2 compatibility is provided through the legacy `swagger-compat-spec-parser` module:

io.swagger.parser.v3:swagger-parser:2.1.23
└── io.swagger.parser.v3:swagger-parser-v2-converter:2.1.23
├── io.swagger:swagger-parser:1.0.71
└── io.swagger:swagger-compat-spec-parser:1.0.71
├── com.github.java-json-tools:json-schema-validator:2.2.14
│ └── com.github.java-json-tools:json-schema-core:1.2.14
│ └── com.github.java-json-tools:jackson-coreutils:2.0
└── com.github.java-json-tools:json-patch:1.13
└── com.github.java-json-tools:jackson-coreutils:2.0


`jackson-coreutils:2.0` is currently being reported for:

- CVE-2026-86513
- CVE-2026-86511
- CVE-2026-86321

Is there a supported release, replacement dependency, or recommended remediation that removes or patches `jackson-coreutils:2.0` while retaining:

- Swagger 1.2 conversion
- Java 8 compatibility
- Swagger 2.0 and OpenAPI 3 parsing

We understand that Swagger Parser 2.x does not document native support for Swagger 1.2. In our case, that behavior is coming from the transitive `swagger-compat-spec-parser:1.0.71` module.

We would prefer an upstream-supported solution rather than maintaining a private fork.

## Affected Version

`io.swagger.parser.v3:swagger-parser:2.1.23`

Runtime: Java 8

## Context

We tested the following configurations:

1. With all dependencies present:
   - Swagger 1.2 parsing succeeds
   - Swagger 2.0 parsing succeeds
   - OpenAPI 3 parsing succeeds

2. After removing only `jackson-coreutils`:
   - Swagger 2.0 and OpenAPI 3 parsing still succeed
   - Swagger 1.2 parsing fails with:

java.lang.NoClassDefFoundError:
com/github/fge/jackson/jsonpointer/JsonPointer


3. After excluding the legacy `swagger-compat-spec-parser` dependency chain:
   - Swagger 2.0 and OpenAPI 3 parsing succeed
   - Swagger 1.2 is no longer parsed

This indicates that `jackson-coreutils` is required at runtime specifically by the legacy Swagger 1.2 compatibility path.

We would appreciate guidance on the preferred upstream solution:

1. Is `swagger-compat-spec-parser` still maintained, and would a dependency-remediation PR be considered?
2. Is there an existing Java 8-compatible replacement or patched release?
3. Should remediation be proposed in this repository, or directly in the `jackson-coreutils` project?
4. Is removal of Swagger 1.2 support now the only supported migration path?

## Additional Details

Related upstream reports:

- https://github.com/java-json-tools/jackson-coreutils/issues/64
- https://github.com/java-json-tools/jackson-coreutils/issues/65
- https://github.com/java-json-tools/jackson-coreutils/issues/66
Lingua principale
Java
Stelle
870
Fork
565
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di swagger-api/swagger-parser

Tutte le issue di swagger-api/swagger-parser

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.