gitsafehub
github.com/gastaldi/quarkus-neo4j ↗

gastaldi/quarkus-neo4j

scanned 2026-08-10 · git af92509
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies11Known OSS vulnerabilities2Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 11 found · 1 serious

Packages you depend on that have known security holes (CVEs).

  • Serious CVE-2022-4116 quarkus_dev_ui: Dev UI Config Editor is vulnerable to drive-by localhost attacks leading to RCE
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2022-4116). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-2700 quarkus-core: Leak of local configuration properties into Quarkus applications
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2024-2700). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-2974 quarkus-core: TLS protocol configured with quarkus.http.ssl.protocols is not enforced, client can enforce weaker supported TLS protocol
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2023-2974). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-5675 quarkus: Authorization flaw in Quarkus RestEasy Reactive and Classic when "quarkus.security.jaxrs.deny-unannotated-endpoints" or "quarkus.security.jaxrs.default-roles-allowed" properties are used.
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2023-5675). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-4147 quarkus-vertx-http: Security misconfiguration of CORS : OWASP A05_2021 level in Quarkus
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2022-4147). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-4853 quarkus: HTTP security policy bypass
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2023-4853). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-39852 io.quarkus:quarkus-vertx-http: io.quarkus:quarkus-vertx-http: Authorization bypass via semicolons in HTTP requests
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2026-39852). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50559 io.quarkus/quarkus-vertx-http: Quarkus: Authorization bypass in HTTP path-based policies via encoded characters
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2026-50559). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-0044 quarkus-vertx-http: a cross-site attack may be initiated which might lead to the Information Disclosure
    integration-tests/pom.xml
    A package you depend on has a known security hole (CVE-2023-0044). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-2700 quarkus-core: Leak of local configuration properties into Quarkus applications
    runtime/pom.xml
    A package you depend on has a known security hole (CVE-2024-2700). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-2974 quarkus-core: TLS protocol configured with quarkus.http.ssl.protocols is not enforced, client can enforce weaker supported TLS protocol
    runtime/pom.xml
    A package you depend on has a known security hole (CVE-2023-2974). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 2 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-rqfh-9r24-8c9r AssertJ has XML External Entity (XXE) vulnerability when parsing untrusted XML via isXmlEqualTo assertion
    /workdirs/scan-e9d1b136-c800-4649-9758-567e2e63a632/deployment/pom.xml
    A package you depend on has a known security hole (CVE-2026-24400). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rqfh-9r24-8c9r AssertJ has XML External Entity (XXE) vulnerability when parsing untrusted XML via isXmlEqualTo assertion
    /workdirs/scan-e9d1b136-c800-4649-9758-567e2e63a632/runtime/pom.xml
    A package you depend on has a known security hole (CVE-2026-24400). Fix: Update that package to its patched version.

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ none found ✓

Packages that look intentionally malicious: typosquats, sneaky install scripts.

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.