gitsafehub
github.com/conduktor/conduktor-gateway-soak-func ↗

conduktor/conduktor-gateway-soak-func

scanned 2026-08-06 · git 20a3832
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 secrets35Vulnerable dependencies✓Known OSS vulnerabilities26Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ 35 found · 34 serious

API keys, passwords or tokens committed into the repo.

  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    README.md:42
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    README.md:49
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    README.md:73
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    README.md:152
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    README.md:164
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    README.md:199
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario3.yaml:33
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario3.yaml:40
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario2.yaml:26
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario2.yaml:33
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario4.yaml:16
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario2.yaml:56
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario3.yaml:64
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario4.yaml:22
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario4.yaml:34
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario2.yaml:26
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario2.yaml:33
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario2.yaml:56
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario4.yaml:16
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario4.yaml:22
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario4.yaml:34
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario3.yaml:33
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario3.yaml:40
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario3.yaml:64
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
    config/scenario/scenario4.yaml:12
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
… 10 more not shown

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ none found ✓

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

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 26 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-78wr-2p64-hpwj Apache Commons IO: Possible denial of service attack on untrusted input to XmlStreamReader
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2024-47554). Fix: Update that package to its patched version.
  • Worth fixing GHSA-2x2g-32r7-p4x8 Apache Kafka Clients: Privilege escalation to filesystem read-access via automatic ConfigProvider
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2024-31141). Fix: Update that package to its patched version.
  • Worth fixing GHSA-5qcv-4rpc-jp93 Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-35554). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vgq5-3255-v292 Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2025-27817). Fix: Update that package to its patched version.
  • Worth fixing GHSA-wf66-mphr-4c4r Apache Kafka exposes sensitive information in its DEBUG logs
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-33558). 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-69e47c13-aac4-4d21-bcea-163226d9276b/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-72hv-8253-57qq jackson-core: Number Length Constraint Bypass in Async Parser Leads to Potential DoS Condition
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-18401). Fix: Update that package to its patched version.
  • Worth fixing GHSA-r7wm-3cxj-wff9 jackson-core: Async parser maxNumberLength bypass via chunked digit accumulation (incomplete fix for GHSA-72hv-8253-57qq)
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-3pjw-73gf-8qr5 jackson-databind: @JsonIgnore on a Record property is bypassed with a PropertyNamingStrategy
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-59888). Fix: Update that package to its patched version.
  • Worth fixing GHSA-5jmj-h7xm-6q6v jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnoreProperties
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-54515). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hgj6-7826-r7m5 jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF)
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-54514). Fix: Update that package to its patched version.
  • Worth fixing GHSA-j3rv-43j4-c7qm jackson-databind has a PolymorphicTypeValidator bypass via generic type parameters that allows arbitrary class instantiation
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-54512). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rmj7-2vxq-3g9f jackson-databind has an array subtype allowlist bypass in BasicPolymorphicTypeValidator (allowIfSubTypeIsArray)
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-54513). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4265-ccf5-phj5 Apache Commons Compress: OutOfMemoryError unpacking broken Pack200 file
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2024-26308). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4g9r-vxhx-9pgx Apache Commons Compress: Denial of service caused by an infinite loop for a corrupted DUMP file
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2024-25710). Fix: Update that package to its patched version.
  • Worth fixing GHSA-j288-q9x7-2f5v Apache Commons Lang is vulnerable to Uncontrolled Recursion when processing long inputs
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2025-48924). Fix: Update that package to its patched version.
  • Worth fixing GHSA-3pxv-7cmr-fjr4 Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-34480). Fix: Update that package to its patched version.
  • Worth fixing GHSA-6hg6-v5c8-fphq Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-34477). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vc5p-v9hr-52mj Apache Log4j does not verify the TLS hostname in its Socket Appender
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2025-68161). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cmp6-m4wj-q63q yawkat LZ4 Java has a possible information leak in Java safe decompressor
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2025-66566). Fix: Update that package to its patched version.
  • Worth fixing GHSA-vqf4-7m7x-wgfc LZ4 Java Compression has Out-of-bounds memory operations which can cause DoS
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2025-12183). Fix: Update that package to its patched version.
  • Worth fixing GHSA-xx22-p4ch-683r LZ4 Java: Native XXHash implementations can crash the JVM when passed invalid byte array ranges
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2026-59949). Fix: Update that package to its patched version.
  • Worth fixing GHSA-55g7-9cwv-5qfv snappy-java's missing upper bound check on chunk length can lead to Denial of Service (DoS) impact
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2023-43642). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fjpj-2g6w-x25r snappy-java's Integer Overflow vulnerability in compress leads to DoS
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2023-34454). Fix: Update that package to its patched version.
  • Worth fixing GHSA-pqr6-cmr2-h8hf snappy-java's Integer Overflow vulnerability in shuffle leads to DoS
    /workdirs/scan-69e47c13-aac4-4d21-bcea-163226d9276b/pom.xml
    A package you depend on has a known security hole (CVE-2023-34453). Fix: Update that package to its patched version.
… 1 more not shown

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.