API Security
API security addresses the unique vulnerabilities that arise when applications expose functionality through programmatic interfaces. As organizations shift to API-first architectures, microservices, and third-party integrations, APIs have become the primary attack surface for modern applications. The OWASP API Security Top 10 identifies critical risks including Broken Object Level Authorization (BOLA), mass assignment, excessive data exposure, and lack of rate limiting. APIs often inadvertently expose more data than their UI counterparts, accept parameters that bypass frontend validation, and may lack the authentication and authorization checks that browser-based interfaces enforce. REST, GraphQL, gRPC, and WebSocket APIs each present distinct security challenges. Effective API security requires authentication hardening, input validation, output filtering, rate limiting, proper error handling, and comprehensive logging across every endpoint.
APIs removed the UI, and the UI was doing more security work than anyone admitted
In a server-rendered application, the interface constrained the request: you saw the fields the form had, the actions your role rendered, the pages the navigation offered. None of that was access control, but it shaped what most users ever sent. An API exposes the operations directly, in a documented and enumerable form, and everything the interface was implicitly limiting is now explicit surface.
That explains why the API-specific vulnerability lists look the way they
do. Object-level authorization tops them because a REST resource is an
identifier in a URL and there is nothing but a server-side check between a
caller and any record. Mass assignment follows: modern frameworks bind request
bodies to model objects automatically, so an unlisted field like
role, verified or account_id may be
accepted simply because nobody enumerated what the endpoint should accept.
Excessive data exposure is the response-side version — the endpoint returns
the whole serialized object and the client displays a subset, so the fields the
UI hides are still in the payload.
Discovery is a large part of the work and rewards attention to
documentation formats. OpenAPI and Swagger definitions, GraphQL introspection,
mobile client bundles and JavaScript chunks routinely describe endpoints that
are live but undocumented — older API versions in particular, which are kept
for compatibility and stop receiving the security review the current version
gets. Comparing /v1 against /v2 for checks that
exist in one and not the other is a reliable technique.
Rate limiting and resource controls matter more here than in web applications, because an API is designed for programmatic access and distinguishing legitimate automation from abuse is genuinely hard. Batching and aliasing defeat naive per-request counting.
The entries below cover REST and GraphQL, testing methodology and the schema-enforcement side of defence.
| Date Added | Link | Excerpt |
|---|---|---|
| 2026-11-19 NEW 2026 | I Changed USER to ADMIN in a JWT. Here’s Why the API Rejected It. intermediate AuthN JWT | This article explores a security vulnerability related to JSON Web Tokens (JWTs). The author details an attempt to change a user's role from "USER" to "ADMIN" within a JWT. However, the API rejected this modification. The piece likely explains the underlying security mechanisms that prevented this unauthorized privilege escalation, highlighting how JWTs are designed to be tamper-resistant and what specific checks the API performed to identify the altered token. The focus is on the technical reasons behind the API's rejection of the modified JWT. |
| 2026-11-19 NEW 2026 | Authentication vs Authorization: The Difference, and How to Actually Secure an API beginner AuthN AuthZ | Authentication verifies who a user is, while authorization determines what they can access. Misunderstanding this distinction is a primary cause of API breaches. Effective API security requires robust implementation of both authentication and authorization mechanisms to prevent unauthorized access and data compromise. |
| 2026-11-19 NEW 2026 | Building API Swarm Pentest: An Evidence-First API Security Scanner intermediate | API Swarm Pentest is an evidence-first API security scanner presented as a scope-enforced CLI tool. It aims to make API security testing safer, more auditable, and reproducible. The tool addresses common challenges in API security testing by providing a structured approach. |
| 2026-11-19 NEW 2026 | Twitter Privacy Bypass: Hidden Accounts Found by Email news Bug Bounty | A $5,040 bounty was awarded for discovering a Twitter privacy bypass. The vulnerability, present in the Android login flow, allowed users to link an email or phone number to a hidden account. Details the root cause of this issue, its impact on user privacy, and the implemented fixes. → masimshahzad.medium.com |
| 2026-11-19 NEW 2026 | Starbucks Path Traversal: Nearly 100M Customer Records news Bug Bounty | A path traversal vulnerability in a Starbucks proxy API exposed an internal search service, potentially compromising nearly 100 million customer records. This flaw allowed unauthorized access to sensitive data. The content details the root cause of the vulnerability, its significant impact on customer privacy, and the necessary fixes implemented by developers to address the security loophole. → masimshahzad.medium.com |
| 2026-11-18 NEW 2026 | Why Your Mobile App Is Only as Secure as Its API beginner Mobile | This content emphasizes that a mobile app's security is fundamentally tied to the security of its backend API. The author highlights that even a well-secured mobile application is vulnerable if its API, which handles data and functionality, is compromised. The article suggests that developers should prioritize API security as much as, if not more than, the client-side security of the mobile app itself. |
| 2026-11-18 NEW 2026 | A token can be valid and still not be meant for your API intermediate AuthN JWT | Even a valid token doesn't guarantee access to your API. A recent tutorial on securing Kotlin and Spring Boot APIs with OAuth2 and JWT highlighted a common pitfall: tokens can be technically valid (e.g., correctly signed, not expired) but still not intended for use with a specific API. This means developers must implement checks to ensure the token's issuer or audience matches their API's requirements. Simply verifying token validity isn't enough to prevent unauthorized access. |
| 2026-11-18 NEW 2026 | One API Request Exposed 14,000+ Email Addresses news Bug Bounty | A single API request vulnerability led to the exposure of over 14,000 email addresses. What began as a minor issue escalated into a significant data breach. The vulnerability allowed unauthorized access to a substantial number of email addresses. |
| 2026-11-18 NEW 2026 | ProtoSpector: Burp extension for Protobuf and gRPC testing (Doyensec) intermediate Burp | Library: ProtoSpector is a Burp Suite extension for testing gRPC services, automatically decoding and encoding Protocol Buffer messages. It supports white-box testing with `.proto` schemas and black-box testing through automatic structure inference, offering inline editing of descriptors and a type preview system. ProtoSpector integrates with Burp Repeater for gRPC method invocation and detects various Protobuf content types, including auto-generating method descriptors from unknown requests, simplifying security analysis of gRPC traffic. |
| 2026-11-18 NEW 2026 | LLM API Exploitation with Excessive Agency : Portswigger Lab Writeup intermediate AI Burp | This writeup details a PortSwigger lab on LLM API exploitation, specifically focusing on "Excessive Agency." It introduces Large Language Models (LLMs) and their functionality. The lab appears designed for beginners learning LLM security vulnerabilities. The content focuses on demonstrating how LLM APIs can be exploited. |
| 2026-11-18 NEW 2026 | HCL Commerce Storefront REST API XXE intermediate XXE | An XML External Entity (XXE) vulnerability has been identified in the HCL Commerce Storefront REST API. This vulnerability allows attackers to potentially access sensitive information from the server or perform denial-of-service attacks. The issue stems from how the API parses XML input without proper validation, enabling malicious entities to be injected. Users are advised to apply the necessary patches and follow security best practices to mitigate this risk. |
| 2026-11-18 NEW 2026 | Testing GraphQL mutations: the checklist I wish I had before my last outage intermediate GraphQL | This article presents a checklist for testing GraphQL mutations, developed after an outage caused by seemingly successful mutations that failed to update data. The author emphasizes the need to go beyond a 200 OK response and valid JSON. Key considerations include verifying that the mutation actually changes the expected data, handling edge cases, and ensuring data integrity after modifications. The checklist aims to prevent issues where mutations appear successful but do not achieve their intended outcome, leading to user-reported problems. |
| 2026-11-17 NEW 2026 | Amazon Uncovers AI Agent Campaign Targeting LiteLLM, Dify, and Other Apps for API Keys news 6 min read AI Secrets | Library for AI agent threat intelligence, detailing a campaign by attackers using ARTEX and similar tools to target LiteLLM, Dify, One API, Langflow, and RAGFlow by exploiting vulnerabilities like default credentials, unfinished installs, authentication bypasses, and server-side request forgery to steal API keys and cloud credentials. The library highlights techniques used for reconnaissance, including scanning GitHub, npm, PyPI, and Telegram, and emphasizes that the AI agents' effectiveness stems from increased speed and persistence rather than novel attack methods. → thehackernews.com |
| 2026-11-17 NEW 2026 | Test your API against the OWASP API Security Top 10 2023 beginner | This article, originally from the Rokkhe blog on Hashnode and drafted with AI assistance, guides readers on testing their APIs against the OWASP API Security Top 10 2023. It aims to help developers and security professionals understand and mitigate common API security risks by focusing on the updated OWASP list. |
| 2026-11-17 NEW 2026 | Soft-Deleted, Still Editable: BOLA in Munshi’s Invoice API intermediate AuthZ Bug Bounty | Munshi's Invoice API had a vulnerability where authenticated users could edit soft-deleted invoices. This was due to missing ownership and invoice-lifecycle checks. The flaw allowed unauthorized modification of financial data, bypassing intended deletion processes. |
| 2026-11-17 NEW 2026 | GraphQL persisted queries allowlist bypass via ID manipulation intermediate GraphQL | Library for identifying GraphQL persisted query allowlist bypass vulnerabilities, specifically detailing CVE-2026-22014. This bypass occurs when a server falls back to executing a provided query instead of rejecting requests with unknown `queryId` values, enabling attackers to execute arbitrary GraphQL queries. The exploit involves sending a mixed payload with a non-existent `queryId` alongside the malicious query. |
| 2026-11-16 NEW 2026 | OWASP #5: Broken Function Level Authorization (When Users Execute Forbidden Actions) beginner AuthZ | OWASP Top 10 #5 highlights Broken Function Level Authorization, a critical API security vulnerability. This flaw allows unauthorized users to access or manipulate functionalities they shouldn't be able to, going beyond just data exposure. While data protection is important, the focus here is on preventing users from performing forbidden actions, ensuring that only authorized individuals can execute specific functions within an application or API. This vulnerability can lead to a range of security breaches if not properly addressed. |
| 2026-11-16 NEW 2026 | The Internal Tool T-Mobile Forgot Was Facing the Public Internet beginner Bug Bounty | T-Mobile's internal tool was accidentally exposed to the public internet, creating a significant API security vulnerability. This oversight highlights the critical need for robust API security practices, as even seemingly simple vulnerabilities can have serious consequences. The incident serves as a cautionary tale for organizations to ensure their internal tools and sensitive data are properly protected and not inadvertently accessible from the public domain. |
| 2026-11-16 NEW 2026 | VoAPI SQL injection intermediate SQLi | VoAPI versions 1.0.0 through 1.2.0 are vulnerable to SQL injection. This vulnerability allows an attacker to execute arbitrary SQL commands on the database. The exploit involves manipulating input fields, leading to unauthorized data access or modification. Users are advised to update to a patched version to mitigate this security risk. |
| 2026-11-16 NEW 2026 | OWASP #7: Server-Side Request Forgery (SSRF) — Trick Your Server beginner SSRF | Server-Side Request Forgery (SSRF) is a vulnerability where an attacker can trick a server into making unintended requests to internal or external resources. Modern applications often fetch data from external services, creating potential attack vectors. By manipulating user-supplied URLs or parameters, attackers can exploit this by forcing the server to communicate with systems it shouldn't, potentially leading to unauthorized access or data exposure. This highlights the critical need for strict validation and sanitization of all user-provided input when interacting with external resources. |
| 2026-11-16 NEW 2026 | Kong graphql-proxy-cache-advanced leaks cached responses across callers intermediate GraphQL | The graphql-proxy-cache-advanced plugin in Kong Gateway has a vulnerability that allows cached responses to be leaked between different callers. This means that one user's sensitive data could be exposed to another user if they make requests that share cached information. This issue affects specific configurations of the plugin. |
| 2026-11-15 NEW 2026 | NocoDB authentication bypass in oauth-token.service news AuthN | NocoDB versions prior to 2026.08.1 have a security vulnerability allowing authentication bypass. This flaw resides within the oauth-token.service component, potentially exposing sensitive data and systems to unauthorized access. Users are advised to update to a patched version to mitigate this risk. |
| 2026-11-15 NEW 2026 | Pulse missing authorization in /api/ai news AI AuthZ | Advisory for Pulse v5.0.17 through v6.7.0, detailing a missing authorization vulnerability in `/api/ai/approvals` endpoints. Authenticated viewer-level users can manage approval requests, leading to exposure of proposed commands and targets. Attackers can also approve or deny other users' requests, impacting decision and audit states. |
| 2026-11-15 NEW 2026 | Exploiting All 10 OWASP API Security Risks in vAPI (+ Bonus Arena Challenges) intermediate AuthN AuthZ Bug Bounty | This content details a practical exploration of all ten OWASP API Security Risks using vAPI. The walkthrough covers the discovery and exploitation of vulnerabilities such as Broken Object Level Authorization and Broken Authentication. It also includes bonus challenges from an arena. |
| 2026-11-15 NEW 2026 | graphql-orm-router: HTTP SSE/multipart subscriptions bypass WebSocket gateway auth controls news 4 min read AuthN AuthZ GraphQL | Library for securing GraphQL endpoints, addressing vulnerabilities where HTTP Server-Sent Events (SSE) and multipart subscriptions bypass WebSocket gateway authentication and authorization controls. The issue, identified as RTR-2 and initially rated Medium, allows unauthenticated access to subscriptions and bypasses token expiry checks and attempt limiters. The vulnerability stems from the router's handling of HTTP subscription requests, which do not undergo the same rigorous checks as WebSocket connections, potentially leading to unauthorized data access. Fixes involve enforcing principal and expiry for HTTP streams or rejecting subscriptions originating from untrusted internal paths. |
| 2026-11-15 NEW 2026 | GraphQL's blind spots: introspection, batching, and nested queries beginner 12 min read GraphQL | Library on GraphQL security vulnerabilities arising from its core features. It details how introspection, batching, and nested queries, while beneficial for developers, present significant attack surfaces. The resource highlights techniques attackers use, such as leveraging introspection for reconnaissance via tools like InQL and exploiting batching for rate limit bypass on login or OTP brute force. It emphasizes that security controls are configuration decisions, recommending disabling introspection in production, implementing operation-level rate limiting, and enforcing field-level authorization to mitigate these risks. |
| 2026-11-15 NEW 2026 | GraphQL penetration testing beyond introspection intermediate 11 min read GraphQL | Library for GraphQL security testing that goes beyond simply disabling introspection. It details how to identify vulnerabilities such as Broken Object Level Authorization (BOLA) by testing node ID lookups, and how attackers can bypass rate limiting through query batching and alias-based brute force. The library also covers testing for resource exhaustion via query depth and complexity, and securing the write path by scrutinizing mutations for issues like mass assignment. |
| 2026-11-15 NEW 2026 | GraphQL batching abuse and how to stop it intermediate 3 min read GraphQL | Library for detecting and mitigating GraphQL batching abuse, where aliasing and array batching allow single HTTP requests to execute numerous operations, bypassing naive rate limiters. It details techniques for testing abuse, such as aliased logins and array batching, and highlights tools like InQL and graphql-cop. The library offers remediation strategies including counting aliases per request, disabling HTTP batching, and adopting persisted queries, exemplified by a fix implemented for a fintech using graphql-armor-max-aliases. |
| 2026-11-15 NEW 2026 | Offense and defense in GraphQL: introspection, batching, and depth abuse intermediate 4 min read GraphQL | Library for securing GraphQL APIs, focusing on defense mechanisms within the execution layer rather than relying solely on HTTP transport. It addresses schema discovery via introspection, rate-limit evasion using field aliasing and batching, and resource exhaustion through deeply nested queries. The library provides strategies for implementing query depth limits and query cost analysis, preventing vulnerabilities like unintentional schema exposure and denial-of-service attacks. |
| 2026-11-14 NEW 2026 | Critical Apache HTTP Server vulnerability can allow remote code execution (CVE-2026-119618) news 2 min read RCE | Analysis of CVE-2026-119618, a critical race condition in Apache HTTP Server's mod_http2 module. This vulnerability, reported by Anthropic and Google, allows unauthenticated remote attackers to execute arbitrary code by exploiting heap corruption in the `assign_headers()` function. Mitigation includes upgrading to Apache HTTP Server 2.4.71 or later, disabling HTTP/2, or applying vendor-specific OS package updates. Load balancers may mitigate exposure in some setups. → aikido.dev |
| 2026-11-14 NEW 2026 | The key you shipped to every visitor intermediate Secrets | A security researcher discovered a live API key with write access embedded directly within a website's JavaScript bundle. This means every visitor to the site unknowingly downloaded the key, potentially exposing sensitive data and operations to unauthorized access. The vulnerability highlights a critical oversight in how sensitive credentials are managed in web development. |
| 2026-11-14 NEW 2026 | WuppieFuzz 1.8.1: REST API fuzzer adds Web Fuzzing Commons reports and injection signatures intermediate 7 min read Fuzzing | Library for fuzzing REST APIs, WuppieFuzz, now supports Web Fuzzing Commons schema reports with replayable test cases and enhanced HTML coverage reports. Version 1.8.1 refines injection signature detection, differentiating between LDAP, SQL, NoSQL, command, and XSS injections, alongside specific HTTP 5xx response criteria. Previous versions introduced grammar-based mutation for SQLi, XSS, SSTI, command/LDAP/NoSQL injection, path traversal, XXE, and format strings, alongside crash deduplication and OpenTelemetry coverage guidance. |
| 2026-11-14 NEW 2026 | doyensec/ProtoSpector: Burp Suite extension for Protobuf/gRPC testing intermediate 3 min read Burp | Library for security testing of Protobuf and gRPC messages within Burp Suite. ProtoSpector supports both whitebox testing with pre-loaded `.proto` schemas and blackbox testing that infers message structure. It enables automatic detection of Protobuf content types, inline editing of decoded messages, type previewing, and seamless integration with Burp's Repeater for gRPC requests. |
| 2026-11-14 NEW 2026 | Schemathesis 4.33.0: GraphQL coverage phase and unary gRPC fuzzing intermediate 4 min read Fuzzing GraphQL Python | Library adding a coverage phase for GraphQL schemas to check for missing or mistyped fields, and fuzzing unary gRPC methods. It supports XML request bodies following OpenAPI 3.2 nodeType, and cookie parameters with OpenAPI 3.2 style: cookie. This release includes performance improvements for pytest collection and fixes numerous issues related to data generation, request serialization, XML handling, GraphQL schema loading, checks, authentication, timeouts, outages, test execution, and reporting. |
| 2026-11-14 NEW 2026 | What is GraphQL security testing? beginner 10 min read GraphQL | Library for assessing GraphQL API security, focusing on exploiting query interfaces, schemas, and resolver logic. This library identifies risks unique to GraphQL, such as open introspection enabling schema enumeration, field-level authorization vulnerabilities, and resource exhaustion via batch or nested queries. It combines schema analysis, adversarial querying, and code review to uncover vulnerabilities missed by standard REST API testing methods. |
| 2026-11-14 NEW 2026 | Confirming GraphQL DAST findings: introspection, batching, depth/cost, CSRF over GET intermediate 16 min read CSRF GraphQL | Library for confirming Dynamic Application Security Testing (DAST) findings against GraphQL endpoints, focusing on introspection, field suggestions, alias-based batching, GET method support, and error masking. It details how scanner observations, such as enabled introspection or GET support, can be misleading and do not necessarily indicate vulnerabilities. The library guides users to look beyond configuration properties and investigate the actual impact of exposed fields, rate limiting, and error handling by referencing specific techniques and potential misconfigurations. |
| 2026-11-14 NEW 2026 | NocoDB 2026.09.0 insecure direct object reference news AuthZ IDOR | NocoDB versions prior to 2026.09.0 have an insecure direct object reference (IDOR) vulnerability. This flaw allows unauthorized access to data and potentially sensitive information. The vulnerability is fixed in version 2026.09.0. Users are strongly advised to upgrade to the latest version to mitigate this security risk. |
| 2026-11-13 NEW 2026 | Inside Cirro: Enumeration as a Restricted Guest intermediate 10 min read AuthZ | Tool for enumerating Entra applications and service principals as a restricted guest user. It traverses known application IDs via HTTP GET requests to identify applications, bypassing Entra ID's most restrictive guest settings that block traditional directory enumeration. The tool leverages the ability of restricted guests to read application properties and permissions, a gap left by existing enumeration tools like AzureHound and ROADtools. → bishopfox.com |
| 2026-11-13 2026 | A Reader’s Comment Made Me Scan 150 APIs intermediate | A reader's comment prompted a security researcher to scan 150 APIs. The comment highlighted an overlooked login check in a group of APIs, which otherwise functioned correctly. This observation led to a broader security review of numerous APIs, suggesting that even seemingly minor oversights can have significant implications for overall API security. |
| 2026-11-13 2026 | I Turned a Rigid, Hardcoded Role System into a Dynamic RBAC Architecture, Without Breaking a Single… intermediate AuthZ | This article details the transformation of a rigid, hardcoded role system into a dynamic Role-Based Access Control (RBAC) architecture. The author achieved this by implementing permission slugs, a role-mapping layer, and backend-enforced checks. These changes created a scalable authorization system without disrupting existing functionality. |
| 2026-11-13 2026 | Introducing ProtoSpector: A Burp Suite Extension for Analyzing, Tampering With, and Testing Protobuf and gRPC Traffic intermediate 2 min read Burp | Extension that analyzes, tampers with, and tests Protobuf and gRPC traffic within Burp Suite. ProtoSpector automatically decodes messages using provided .proto schemas or infers structures for black-box testing. It allows inline editing of inferred descriptors, type previewing, and seamless integration with Burp Repeater for gRPC testing. Supported content types include `application/grpc-web+proto` and `application/x-protobuf`. → blog.doyensec.com |
| 2026-11-13 2026 | GraphQL security testing and pentest checklist beginner 9 min read GraphQL | Checklist for GraphQL security testing, identifying vulnerabilities like authorization gaps, denial-of-service vectors, and data leaks. It details testing techniques for common GraphQL flaws including introspection abuse, object and field-level authorization bypass (BOLA/IDOR), batching and alias abuse for rate limit evasion, denial of service via query complexity, injection through resolvers, and CSRF risks via improper request-method handling. The checklist emphasizes manual testing for authorization flaws, which scanners often miss, and covers fingerprinting servers with tools like graphw00f. |
| 2026-11-13 2026 | Foreman PersonalAccessTokensController IDOR news AuthZ IDOR | Writeup of CVE-2026-86322 in Foreman, detailing an Insecure Direct Object Reference (IDOR) vulnerability within the Api::V2::PersonalAccessTokensController. This flaw allows an authenticated attacker with `create_personal_access_tokens` permission to forge Personal Access Tokens for other users by exploiting missing authorization checks during user resolution. Successful exploitation can lead to account takeover, including administrator privileges, by using the compromised token to authenticate as the victim. |
| 2026-11-13 2026 | GraphQL BOLA: one object, many paths, and how to prove the gap intermediate 10 min read AuthZ GraphQL IDOR | Library for identifying and exploiting GraphQL Broken Object Level Authorization (BOLA) vulnerabilities. It details how to enumerate all object access paths from a schema, including those exposed via interfaces like `Node` and mutations, and systematically test them using two accounts in a single request. This approach enables the verification of authorization gaps without direct data access, referencing OWASP API Security Top 10 2023 (API1:2023) and the OWASP GraphQL Cheat Sheet. |
| 2026-11-12 2026 | Stolen AI API Keys: What Railway’s Breach Report Teaches About Agent Credentials beginner AI Secrets | Railway's recent breach highlights critical security risks associated with AI API keys, often referred to as "agent credentials." The report emphasizes that these keys, when compromised, can grant attackers extensive access to sensitive data and services. It underscores the necessity for robust security measures to protect these credentials, recommending practices such as strict access controls, regular key rotation, and comprehensive monitoring to prevent unauthorized usage and potential exploitation. The incident serves as a stark reminder for companies to prioritize the security of their AI infrastructure and the credentials that power it. |
| 2026-11-12 2026 | GraphQL injection in Chatwoot's Linear integration intermediate GraphQL | Library for detecting GraphQL injection vulnerabilities, exemplified by the recent flaw in Chatwoot's Linear integration. This vulnerability allowed attackers to manipulate `team_id` and `link_id` arguments, injecting GraphQL syntax to alter requests targeting the Linear API by failing to properly escape these interpolated values. |
| 2026-11-12 2026 | GraphQL introspection: disabling it leaves the field open intermediate 6 min read AuthZ GraphQL | Library providing a downloadable Python fixture to test GraphQL introspection vulnerabilities in graphql-core 3.2.14. The experiment demonstrates how disabling introspection alone does not prevent unauthorized access to sensitive fields like `adminUserRecord`, which can still be queried if authorization checks are not implemented within resolvers. The fixture includes configurations for introspection enabled/disabled and authorization checks on/off, along with recorded responses and curl commands for verification. |
| 2026-11-12 2026 | Overgrowth: GraphQL aliased-mutation brute force of a password reset (HI CyberCon 2026) intermediate 1 min read AuthN GraphQL | Tool for brute-forcing GraphQL password resets; exploits aliased mutations to attempt all 10,000 four-digit codes within seconds, bypassing rate limits and gaining administrative access to retrieve flags. The technique reconstructs the hidden GraphQL schema from error messages to identify the vulnerable `resetPassword` functionality, as demonstrated in the Overgrowth API example. |
| 2026-11-12 2026 | WuzAPI through 1.1.0 cross-tenant information disclosure intermediate AuthZ | Writeup on CVE-2026-126807, a cross-tenant information disclosure vulnerability in WuzAPI versions up to 1.1.0. The vulnerability resides in the GetHistory handler, allowing authenticated users to access other tenants' chat metadata, including internal user IDs, stored chat JIDs, and last-message times, by exploiting the `GET /chat/history` endpoint with `chat_jid=index`. |
| 2026-11-11 2026 | Supabase Security findings why RLS is only 25% of the issues intermediate 25 min read AuthZ | Library for identifying vulnerabilities in Supabase applications; while Row-Level Security (RLS) issues accounted for only 25% of findings, attackers could exploit other flaws to access sensitive data like PII, private conversations, and payment details. The library's analysis highlights common bypasses of authentication and registration controls, as well as database tables exposed via the REST API and inadequate Postgres access controls, emphasizing the need for comprehensive security testing beyond RLS. |
Frequently Asked Questions
- What is the OWASP API Security Top 10?
- The OWASP API Security Top 10 is a list of the most critical API security risks, including Broken Object Level Authorization (BOLA), Broken Authentication, Broken Object Property Level Authorization, Unrestricted Resource Consumption, Broken Function Level Authorization, Server Side Request Forgery, Security Misconfiguration, and Lack of Protection from Automated Threats.
- Why are APIs harder to secure than web applications?
- APIs often expose more data and functionality than web UIs, accept complex input formats, lack the natural access controls of a browser interface, and are harder to monitor. They also tend to grow organically, creating shadow APIs that bypass security controls, and their machine-to-machine nature makes abuse detection more difficult.
- What tools are used for API security testing?
- Common tools include Burp Suite with API-focused extensions, Postman for manual testing, OWASP ZAP for automated scanning, Akto for API inventory and testing, and custom scripts for fuzzing API parameters. For GraphQL APIs, InQL and graphql-cop are essential. API specification files (OpenAPI/Swagger) are valuable for understanding and testing the full attack surface.
Weekly AppSec Digest
Get new resources delivered every Monday.