zaproxy / zaproxy/zaproxy

Resolve external OpenAPI references through ZAP

Open
#7,856 38 comments 0 reactions 1 assignee View on GitHub

@kingthorin is already working on this.

Since Aug 26, 2026.

add-on bug in:openapi third-party
Dominant language
Java
Stars
15.8k
Forks
2.6k
Avg merge
13h 16m
Merged PRs (30d)
17

Description

Using Zap release 2.12.0 stable docker image for API scan script to test openapi endpoint with spec v3.0.3

Looks like ZAP is unable to parse the openapi definition

2023-05-09 15:26:44,515 http://localhost:34426 "GET http://zap/JSON/core/view/urls/ HTTP/1.1" 200 849
2023-05-09 15:26:44,516 Number of Imported URLs: 9
2023-05-09 15:26:44,516 Import warnings: ['Failed to parse OpenAPI definition.\n\njava.lang.NullPointerException']

Is this an expected behavior? Please sugggest.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.