Skip to content

sorona.xyz bug bounty programs

llvm.org Updated

Sorona.xyz runs one public program: a Sorona bug bounty paying up to $1,500.

Top reward
$1,500
Sorona
Programs
1
1 pays cash
Targets in scope
10
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program sorona.xyz runs.

Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

10 targets. 6 excluded.

  • https://llvm.org

    Web

  • Anything in the project running with more privilege than the person who invoked it, or crossing a privilege boundary the caller expected to hold

    Products and areas

  • Clang itself where a defect reaches past compile time into the produced binary rather than stopping at a crash

    Products and areas

  • Code generation across every back end and every target, where the emitted binary is more exploitable than the source called for

    Products and areas

  • compiler-rt in full: the runtime support the compiler links into finished programs, which is the surface the policy actively points reporters at

    Products and areas

  • libc++ and libc++abi, standard library code running inside a very large share of shipped C++ software

    Products and areas

  • lld, the linker, covered by this entry and the default on Android. A linker creates output, so it sits on the stronger side of the tools distinction that runs through this whole category

    Products and areas

  • lldb and the debug information it consumes

    Products and areas

  • MLIR and Flang, both part of the same tree and covered by the same process

    Products and areas

  • The policy takes reports across the whole LLVM project through a dedicated advisory repository, then narrows on what counts. Its own framing is that most miscompilations are ordinary bugs, and that one qualifies when there are clear indications the produced binary becomes significantly easier to exploit

    Products and areas

No target matches. Try part of a host name, such as the company name.

Out of scope 6

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • Arbitrary code execution inside LLVM from a maliciously crafted C, Rust or bitcode input file, ruled out in the policy by name

  • Bugs in clang, clangd or a JIT's optimizer caused by untrusted input. The policy states these parts were never hardened and does not treat them as security sensitive

  • Incorrect use of LLVM's APIs by a calling project

  • Miscompilations with no clear indication that the produced binary became significantly easier to exploit, which the policy treats as ordinary correctness bugs

  • Sanitizer defects. The policy states most sanitizers are not considered security sensitive

  • Unwinding and exception handling

Recent changes

Reward and scope changes across every sorona.xyz program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in sorona.xyz products, from the NVD.

Search NVD
  • llvm-project commit fdbc55a5 was discovered to contain a segmentation fault via the component mlir::IROperand<mlir::OpOperand.

  • llvm-project commit bd456297 was discovered to contain a segmentation fault via the component mlir::Block::getArgument.

  • llvm-project commit 6c01b5c was discovered to contain a segmentation fault via the component mlir::Type::getDialect().

  • llvm-project commit a0138390 was discovered to contain an assertion failure at !replacements.count(op) && "operation was already replaced.

  • llvm-project commit a0138390 was discovered to contain a segmentation fault via the component mlir::spirv::TargetEnv::TargetEnv(mlir::spirv::TargetEnvAttr).

  • llvm-project commit a0138390 was discovered to contain a segmentation fault via the component matchAndRewriteSortOp<mlir::sparse_tensor::SortOp>(mlir::sparse_tensor::SortOp.

  • llvm-project commit a0138390 was discovered to contain a segmentation fault via the component mlir::Type::isa<mlir::LLVM::LLVMVoidType.

  • LLVM a0dab4950 has a segmentation fault in mlir::outlineSingleBlockRegion. NOTE: third parties dispute this because the LLVM security policy excludes "Language front-ends ... for which a malicious input file can cause undesirable behavior."

About this page

This page gathers every public program listed under llvm.org: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.