ZERO 1.0 · MISTRAL SMALL 4 (119B MoE) · GATED WEIGHTS & PRIVATE API
CORTEXROUTER LAB · FIND IT BEFORE THEY DO.
CortexRouter Zero 1.0 — Motore 119B MoE di Scoperta Zero-Day
Addestrato su Mistral Small 4 (119 miliardi di parametri, 128 esperti MoE ibridi, ~6,5B attivi per token, contesto 256K), il nostro modello principale individua vulnerabilità complesse di autenticazione, crittografia e memoria su interi repository.
🔒 Pesi non pubblicati — Accesso API su richiesta: Per prevenire abusi, i pesi di CortexRouter Zero 1.0 (119B) non sono rilasciati pubblicamente. Team di sicurezza verificati, produttori software (PSIRT), CERT/CSIRT e partner aziendali possono contattarci per richiedere l'accesso API privato.
119B MoE
Mistral Small 4 · 128 Esperti
256K Tokens
Contesto repository da 256K token
12 HTR
Vulnerabilità zero-day HTR-2026 reali
Gated API
Pesi riservati · Zero Data Retention
Esploratore interattivo di audit profondo del codice
100 % senza JavaScript (0 KB JS): filtra per categoria CWE e fai clic su un caso per esaminare il ragionamento di Zero 1.0.
#01 CWE-287 · Go · JWT Key Loader JWS Header `kid` Path Traversal Loads Predictable Empty Key (`/dev/null`) AUTH / RBAC
1. Frammento di codice sorgente (Esempio sintetico)
// synthetic/jwtauth/verifier.go
func VerifySessionJWT(rawToken string, keyDir string) (*Claims, error) {
hdr, payload, sig, err := splitJWS(rawToken)
if err != nil || hdr.Alg != "HS256" {
return nil, ErrInvalidHeader
}
// Attacker sets kid="../../../dev/null" -> keyBytes is []byte{} (0 bytes)!
keyBytes, err := os.ReadFile(filepath.Join(keyDir, hdr.KeyID + ".key"))
if err != nil { return nil, err }
if !hmac.Equal(sig, computeHMAC256(keyBytes, payload)) {
return nil, ErrBadSignature
}
return parseClaims(payload)
}
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
Auth-Token Expert + Filesystem-Sink Analyzer
02 · CLASSE MITRE CWE
CWE-287 (AUTH / RBAC)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
`Alg == "HS256"` and `hmac.Equal` pass standard JWT linter checks; `.key` suffix hides traversal unless path normalization is traced.
04 · CAUSA RADICE
`filepath.Join(keyDir, hdr.KeyID)` resolves `../` segments outside `keyDir`, allowing an attacker to sign arbitrary admin tokens with a known empty or public file.
05 · PATCH MINIMA
Validate `hdr.KeyID` against strict alphanumeric allowlist (`^[a-zA-Z0-9_-]{1,32}$`) or look up keys in an in-memory map.
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-01","cwe_focus":"CWE-287"}'
#02 CWE-190 · C / Rust FFI · Raster 32-Bit Dimension Overflow (`width * height * 4`) Under-Allocates Pixel Buffer MEMORY / DOS
1. Frammento di codice sorgente (Esempio sintetico)
// synthetic/imgcodec/raster_ffi.c
int decode_rgba_tile(uint32_t width, uint32_t height, const uint8_t *src, size_t src_len) {
if (width > 65535 || height > 65535) return -1;
// 65535 * 65535 * 4 overflows 32-bit uint32_t before widening to size_t!
uint32_t buf_bytes = width * height * 4;
uint8_t *rgba = (uint8_t *)malloc(buf_bytes);
if (!rgba) return -1;
return unpack_rows(rgba, width, height, src, src_len); // Out-of-bounds heap write
}
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
Memory-Safety Expert + Integer-Range Solver
02 · CLASSE MITRE CWE
CWE-190 (MEMORY / DOS)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
Explicit upper-bound checks (`width <= 65535`, `height <= 65535`) fool pattern scanners into marking both operands bounded.
04 · CAUSA RADICE
`width * height * 4` wraps modulo `2^32` inside `uint32_t`, allocating a tiny heap buffer followed by multi-megabyte row writes.
05 · PATCH MINIMA
Perform checked `size_t` arithmetic (`__builtin_mul_overflow`) before allocation.
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-02","cwe_focus":"CWE-190"}'
#03 CWE-347 · Python · XML/SAML Auth Signature Verified on First `<Assertion>` While Session Reads Unverified Sibling CRYPTO / SIG
1. Frammento di codice sorgente (Esempio sintetico)
# synthetic/sso/saml_consumer.py
def consume_saml_response(xml_doc: Element) -> str:
sig_node = xml_doc.find(".//ds:Signature", NS)
signed_assertion = sig_node.getparent()
verify_xmldsig(signed_assertion, IDP_CERT) # Verifies signed_assertion only!
# BUG: Queries the document root instead of the verified signed_assertion!
primary_subject = xml_doc.find(".//saml:Assertion/saml:Subject/saml:NameID", NS)
return primary_subject.text
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
Crypto-Protocol Expert + DOM-Tree Provenance Tracker
02 · CLASSE MITRE CWE
CWE-347 (CRYPTO / SIG)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
`verify_xmldsig` cryptographic call is valid and executed unconditionally before reading `NameID`.
04 · CAUSA RADICE
Attacker prepends an unsigned `<saml:Assertion>` before the legitimately signed assertion; `xml_doc.find` returns the attacker's `NameID`.
05 · PATCH MINIMA
Extract `Subject/NameID` strictly from the exact `signed_assertion` subtree returned by `verify_xmldsig`.
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-03","cwe_focus":"CWE-347"}'
#04 CWE-639 · TypeScript · GraphQL Shared Request-Batch DataLoader Leaks Cross-Tenant Invoice Objects AUTH / RBAC
1. Frammento di codice sorgente (Esempio sintetico)
// synthetic/graphql/loaders.ts (singleton cache across HTTP requests!)
const invoiceLoader = new DataLoader<string, Invoice>(async (ids) => {
const rows = await db.query("SELECT * FROM invoices WHERE id = ANY($1)", [ids]);
return ids.map((id) => rows.find((r) => r.id === id));
});
export async function resolveInvoice(_: unknown, args: { id: string }, ctx: AuthCtx) {
if (!ctx.orgId) throw new UnauthorizedError();
return invoiceLoader.load(args.id); // Missing ctx.orgId ownership verification!
}
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
Multi-Tenant Isolation Expert + Async-Lifecycle Analyzer
02 · CLASSE MITRE CWE
CWE-639 (AUTH / RBAC)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
`ctx.orgId` guard is present in resolver and SQL query uses parameterized `$1` binding.
04 · CAUSA RADICE
Module-scoped `DataLoader` caches records across all tenants and never checks `invoice.orgId === ctx.orgId`.
05 · PATCH MINIMA
Instantiate `DataLoader` per request context and filter `WHERE id = ANY($1) AND org_id = $2`.
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-04","cwe_focus":"CWE-639"}'
#05 CWE-362 · Go · Ledger Service Read-Then-Write Balance Check Outside Serializable Transaction Enables Double-Spend CRYPTO / SIG
1. Frammento di codice sorgente (Esempio sintetico)
// synthetic/ledger/withdraw.go
func Withdraw(ctx context.Context, db *sql.DB, acctID string, amount int64) error {
var bal int64
_ = db.QueryRowContext(ctx, "SELECT balance FROM accounts WHERE id=$1", acctID).Scan(&bal)
if bal < amount {
return ErrInsufficientFunds
}
_, err := db.ExecContext(ctx, "UPDATE accounts SET balance = balance - $1 WHERE id=$2", amount, acctID)
return err
}
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
Concurrency & DB-Isolation Expert + State-Invariant Checker
02 · CLASSE MITRE CWE
CWE-362 (CRYPTO / SIG)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
Sequential logic appears sound in single-threaded control-flow analysis.
04 · CAUSA RADICE
Concurrent requests pass `bal < amount` simultaneously before `UPDATE` commits, driving account balance negative.
05 · PATCH MINIMA
Use a single atomic statement: `UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1`.
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-05","cwe_focus":"CWE-362"}'
#06 CWE-918 · TypeScript · Preview Fetch Pre-Fetch IP Blocklist Bypassed via HTTP 302 Redirect to Cloud Metadata WEB / XSS-CSRF
1. Frammento di codice sorgente (Esempio sintetico)
// synthetic/preview/fetcher.ts
export async function fetchRemoteAvatar(rawUrl: string): Promise<ArrayBuffer> {
const parsed = new URL(rawUrl);
const resolvedIp = await dnsLookup(parsed.hostname);
if (isPrivateOrLinkLocalIp(resolvedIp)) {
throw new Error("Blocked internal address");
}
// Default redirect: "follow" silently follows 302 -> http://169.254.169.254/!
const resp = await fetch(parsed.toString(), { signal: AbortSignal.timeout(3000) });
return resp.arrayBuffer();
}
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
Network-Boundary Expert + HTTP-Client Semantics Analyzer
02 · CLASSE MITRE CWE
CWE-918 (WEB / XSS-CSRF)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
`isPrivateOrLinkLocalIp` check is present right before `fetch`, fooling SSRF taint rules.
04 · CAUSA RADICE
Initial URL resolves to an external attacker IP that responds `302 Found` to `http://169.254.169.254/latest/meta-data/`, which `fetch` follows without re-checking.
05 · PATCH MINIMA
Set `redirect: 'error'` (or validate every hop via a custom socket dialer pinning the verified IP).
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-06","cwe_focus":"CWE-918"}'
#07 CWE-22 · Rust · Tar Extractor Two-Entry Symlink + File Tarball Escapes Destination Directory (Symlink Zip-Slip) MEMORY / DOS
1. Frammento di codice sorgente (Esempio sintetico)
// synthetic/archiver/unpack.rs
pub fn unpack_bundle(archive: &mut Archive<File>, dest: &Path) -> io::Result<()> {
for entry in archive.entries()? {
let mut entry = entry?;
let rel = entry.path()?;
if rel.components().any(|c| matches!(c, Component::ParentDir)) {
return Err(io::Error::new(io::ErrorKind::InvalidInput, "parent traversal"));
}
// Entry 1 creates symlink 'dest/sub -> /etc'; Entry 2 writes 'dest/sub/cron.d/job'!
entry.unpack(dest.join(&rel))?;
}
Ok(())
}
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
Filesystem-State Expert + Multi-Step Archive Simulator
02 · CLASSE MITRE CWE
CWE-22 (MEMORY / DOS)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
`Component::ParentDir` (`..`) check blocks lexical path traversal on individual entry names.
04 · CAUSA RADICE
Lexical path check ignores previously extracted symlink entries (`sub -> /etc`), allowing subsequent clean relative paths to write outside `dest`.
05 · PATCH MINIMA
Reject symlink/hardlink archive entries (`EntryType::Symlink`) and use `openat2(..., RESOLVE_BENEATH)`.
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-07","cwe_focus":"CWE-22"}'
#08 CWE-444 · C · Reverse Proxy Parser Tab-Separated `Transfer-Encoding:\tchunked` Triggers CL.TE Request Smuggling WEB / XSS-CSRF
1. Frammento di codice sorgente (Esempio sintetico)
// synthetic/edgeproxy/http_hdr.c
int has_chunked_encoding(const char *hdr_line) {
// Only checks exact ASCII space after colon; misses horizontal tab '\t' or OWS!
return strncasecmp(hdr_line, "Transfer-Encoding: chunked", 26) == 0;
}
2. Output strutturato di CortexRouter Zero 1.0 (119B MoE)
01 · ESPERTI ATTIVATI
RFC-9112 Grammar Expert + Differential Parser Fuzzer
02 · CLASSE MITRE CWE
CWE-444 (WEB / XSS-CSRF)
06 · VERDETTO
✓ CONFIRMED_LOGIC_FLAW
03 · PERCHÉ IL SAST FALLISCE
Code explicitly inspects `Transfer-Encoding` header, appearing to handle chunked framing.
04 · CAUSA RADICE
Edge proxy ignores `Transfer-Encoding:\tchunked` and forwards using `Content-Length`, while RFC-compliant backend parses chunked body—desynchronizing the socket.
05 · PATCH MINIMA
Parse optional whitespace (OWS: SP / HTAB) per RFC 9112 and reject requests containing both `Transfer-Encoding` and `Content-Length`.
3. Esempio di chiamata API privata
curl -s https://api.cortexrouter.ai/v1/audit/completions \
-H "Authorization: Bearer $CORTEXROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"cortexrouter-zero-1.0-119b","reasoning_effort":"high","case_ref":"ZR-DEMO-08","cwe_focus":"CWE-444"}'
Confronto modelli — Zero 1.0 (119B) vs Judge v1 (8B)
| Caratteristica | CortexRouter Zero 1.0 (Modello di punta) | CortexRouter Judge v1 (Verificatore aperto) |
|---|---|---|
| Architettura base | Mistral Small 4 · 119B MoE ibrido (128 esperti, ~6,5B attivi) | Qwen3-8B + Adattatore PEFT LoRA |
| Finestra di contesto | 256.000 token (Intero repository, AST e flussi multi-file) | 32.768 token (Risposta HTTP ed evidenze di laboratorio) |
| Compito principale | Audit profondo del codice sorgente, scoperta zero-day e proposta di patch | Verifica delle prove ed eliminazione dei falsi positivi (80/80 Holdout) |
| Accesso & Licenza | Pesi non pubblicati (Gated) · API privata su richiesta | Pesi aperti Apache-2.0 (Hugging Face & GitHub) |
Richiedere l’accesso privato all’API
- Richiesta aziendale (vahap@cortexrouter.ai): Inviate un’email aziendale (o cifrata OpenPGP) indicando organizzazione e caso d’uso difensivo (PSIRT, AppSec, CI/CD o CERT).
- Verifica d’uso responsabile: L’accesso è concesso esclusivamente a team difensivi verificati, vendor software e ricercatori autorizzati.
- Chiave API dedicata & Zero Retention: Il codice inviato non viene mai salvato né usato per l’addestramento.
- Integrazione JSON: Connessione diretta tramite l’endpoint `/v1/audit/completions`.
Esempio di richiesta e risposta API privata
Schema JSON restituito dall’endpoint autorizzato CortexRouter Zero 1.0:
POST /v1/audit/completions (Request)
{
"model": "cortexrouter-zero-1.0-119b",
"reasoning_effort": "high",
"zero_data_retention": true,
"repository_context": {
"language": "go",
"files": ["auth/grant_router.go", "auth/ticket.go"]
}
}
Structured Audit Diagnostics (Response)
{
"verdict": "VULNERABLE",
"cwe": "CWE-287",
"confidence": 0.98,
"routed_experts": ["auth-state", "cross-branch-taint"],
"call_chain": ["IssueToken -> mintTicketToken"],
"minimal_patch_ready": true
}