Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-66908 — Proof-of-concept reproducer for Apache Camel JWT authentication bypass (CVE-2026-66908) demonstrating missing iss/aud validation in camel-platform-http-main, with Docker-based setup and verification steps. | Kitploit
Tools/GitHubGitHub/oscerd/cve-2026-66908
Vulnerability AnalysisExploitationWeb SecurityAuthenticationLearning & Education
GitHuboscerd/cve-2026-66908

CVE-2026-66908

Proof-of-concept reproducer for Apache Camel JWT authentication bypass (CVE-2026-66908) demonstrating missing iss/aud validation in camel-platform-http-main, with Docker-based setup and verification steps.

View Repository
362 months agoNot yet reviewed
Share

CVE-2026-66908 — camel-platform-http-main JWT iss/aud not validated

Runnable proof-of-concept reproducer for the Apache Camel vulnerability where the camel-main embedded HTTP server builds its JWT authenticator from a keystore alone when neither jwtIssuer nor jwtAudience is configured, so inbound tokens are checked for signature and expiry only — the iss and aud claims are never validated.

RuntimeDirectoryStack
Camel Main (standalone)camel-main/camel-main 4.21.0 + camel-platform-http-main

Why camel-main and not Camel Spring Boot / Camel Quarkus? The vulnerable class, JWTAuthenticationConfigurer, lives in camel-platform-http-main — the camel-main embedded HTTP server (MainHttpServer), used by standalone camel-main applications and camel-jbang. That server is not the Camel Spring Boot platform-http integration (servlet-based) nor the Camel Quarkus one (Quarkus/Vert.x HTTP with its own security), so there is no faithful Spring Boot or Quarkus reproducer for this specific defect. This repository therefore provides a standalone camel-main reproducer, which is the accurate host for the bug.

cd camel-main
mvn clean package
docker compose up -d --build
curl -s http://localhost:8080/exploit
docker compose down

Expected output on an affected build:

[1] GET /protected with NO token                       -> HTTP 401  (auth is enforced)
[2] GET /protected with token iss=https://attacker.example aud=some-unrelated-service  -> HTTP 200  (ACCEPTED — iss/aud NOT validated)
[3] GET /protected with the same token but EXPIRED     -> HTTP 401  (expiry IS checked)
>>> PROVEN: ... the iss and aud claims were never checked ... : true

Vulnerability Summary

PropertyValue
Componentcamel-platform-http-main (the camel-main embedded HTTP server)
CWECWE-287 (Improper Authentication) / CWE-1259 (missing validation of security claims)
Attack vectorA JWT signed by the trusted key (e.g. a shared JWKS) but issued for a different issuer/audience
ImpactAny unexpired token from any party sharing the signing key is accepted — the deployment enforces less than the operator believes
Affected VersionsFrom 4.8.0 before 4.22.0
Fixed Versions4.22.0
JIRACAMEL-24281
Creditn0mi1k

Advisory: https://camel.apache.org/security/CVE-2026-66908.html

The fix

From 4.22.0 the server refuses to start when a JWT keystore is configured but neither jwtIssuer nor jwtAudience is set, naming the missing properties. An operator who genuinely wants signature-and-expiry-only validation must opt in explicitly with camel.server.jwtAllowMissingIssuerAndAudience=true (fail-closed by default):

// fixed (JWTAuthenticationConfigurer.assertIssuerOrAudienceConfigured)
if (ObjectHelper.isEmpty(audience) && ObjectHelper.isEmpty(issuer)) {
    throw new IllegalArgumentException(
        "JWT authentication requires camel.server.jwtIssuer or camel.server.jwtAudience to be configured, ...");
}

Disclaimer

This repository is published for educational and defensive purposes: to help Apache Camel users understand the vulnerability, verify whether they are affected, and confirm that upgrading resolves it. The tokens are minted locally against a throwaway demo keystore bundled in the project. Do not use this material against systems you do not own or operate.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    795
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    520
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    439
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    267
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    264

Explore all tools

Browse our collection of tools

View all tools →