CVE-2026-86516
Received Received - Intake

Improper Privilege Management in MockNest Serverless AWS GitHub OIDC Deployment

Vulnerability report for CVE-2026-86516, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-08

Last updated on: 2026-09-08

Assigner: VulDB

Description

A vulnerability was detected in elenavanengelenmaslova mocknest-serverless 0.9.0. The affected element is an unknown function of the file deployment/aws/shared/github-oidc-role.yaml of the component AWS GitHub OIDC Deployment Helper Script. Performing a manipulation results in improper privilege management. It is possible to initiate the attack remotely. The patch is named 6ab3147282d867c1993f995272750db091c2290b. Applying a patch is the recommended action to fix this issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-08
Last Modified
2026-09-08
Generated
2026-09-08
AI Q&A
2026-09-08
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
elenavanengelenmaslova mocknest-serverless 0.9.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-269 The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
CWE-266 A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves improper privilege management in the MockNest Serverless project's AWS GitHub OIDC Deployment Helper Script. The issue allows remote attackers to manipulate an unknown function in the deployment/aws/shared/github-oidc-role.yaml file, potentially gaining unauthorized privileges.

Detection Guidance

To detect this vulnerability, check if your AWS GitHub OIDC role (github-oidc-role.yaml) has overly permissive IAM policies or trusts the wrong GitHub branches. Review the role's trust policy for StringLike conditions allowing non-main branches and inspect attached policies for excessive permissions like PowerUserAccess.

Impact Analysis

An attacker could exploit this to gain elevated permissions in your AWS environment, leading to unauthorized deployments, data access, or service modifications. This could disrupt testing workflows or expose sensitive integration data stored in S3 or Lambda.

Compliance Impact

This vulnerability could violate compliance requirements by enabling unauthorized access to sensitive data (e.g., API mocks containing personal or health information). GDPR and HIPAA mandate strict access controls; improper privilege management risks data breaches and non-compliance penalties.

Mitigation Strategies

Apply the patch 6ab3147282d867c1993f995272750db091c2290b. Restrict the GitHub Actions OIDC trust policy to the main branch only using StringEquals. Replace broad IAM permissions with scoped ones and create a dedicated CloudFormation execution role with least-privilege permissions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86516. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart