CVE HUNTERReports & history
← CVE HUNTER

RESPONSIBLE RESEARCH

From discovery to reporting

Public record of research by Lima e Silva Tecnologia. We track leads, document analysis and submit reports through private channels.

Last updated: 10/27/2026 · Editorial record based on internal receipts.
Documented analyses8
Technical reports submitted3
Credits received2
CVEs assigned to these cases0
A candidate is not an official CVE. Submission does not mean acceptance or confirmation. This history does not describe observed incidents or exploitation.
3 public advisories · 2 accepted reporter credits

GHSA advisories and credits do not equal CVE assignment. Official sources are linked below.

CH-RP-001Advisories published · credit accepted

Private analysis and technical report

  1. Source review and report prepared

  2. Technical report sent to the official security channel

  3. Published advisories and reporter credit verified on GitHub

NEXT STEP

Track CVE assignment and credit in the second advisory. One advisory lists accepted credit; the other does not yet list the reporter.

CH-RP-002Review completed · not submitted

Documented static analysis

  1. Source reviewed and candidate documented

  2. Communication draft prepared for review

NEXT STEP

Confirm the private channel and complete human review before any submission.

CH-RP-003Report accepted · advisory published

Private-channel submission

  1. Source review and comparison with public advisories completed

  2. Technical report submitted through the official private channel

  3. Report acceptance, advisory publication and reporter credit verified on GitHub

NEXT STEP

Track any CVE assignment. Report and credit accepted on GitHub; no CVE number appears in the advisory.

CH-RP-004Initial contact sent

Confidential routing inquiry

  1. Static analysis and internal report prepared

  2. Request for a confidential channel sent to official support

NEXT STEP

Await the security channel details. Technical details have not yet been submitted.

CH-RP-005Candidate under validation · not submitted

Static analysis with independent review

  1. Public-source triage and second independent assessment completed

NEXT STEP

Confirm scope, applicable version and any previous report through human review before private contact. No CVE has been assigned.

CH-RP-006Preliminary report submitted · awaiting assessment

Static analysis and private report

  1. Static review documented with limitations and version comparison

  2. Preliminary report sent to the official private security channel

NEXT STEP

Await acknowledgment and human assessment. Submission does not mean acceptance, a fix or an assigned CVE.

CH-RP-007Partial review · no report submitted

Static review of a new project

  1. Versioned source recorded and access flows reviewed

  2. Hypotheses compared with safeguards and existing advisories

NEXT STEP

Clarify an authorization question and obtain human validation before classifying a candidate. No new vulnerability confirmed.

CH-RP-008Partial review · no report submitted

Static review guided by project policy

  1. Latest release and security policy checked

  2. Access safeguards and conditions for a potential report documented

NEXT STEP

Keep the static review preliminary. Project submission requirements have not yet been met; no report is ready and no CVE is assigned.

Transparency with confidentiality

These codes are public tracking references, not CVE numbers or external case identifiers. Projects, recipients, private identifiers, evidence, versions and technical details remain confidential during coordinated triage.

This research used static review of public source code, without running projects, reproducing flaws or testing online installations. New steps are recorded after verification; this page does not query mailboxes or private systems in real time.