# CVE-2026-46382: Meeting Room Booking System has server-side request forgery in import functionality

> Attackers can exploit the import functionality to fetch private or local URIs, potentially accessing internal resources or bypassing security controls.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-gh77-mpcm-f8r3

## What is CVE-2026-46382?

CVE-2026-46382 is a high-severity server-side request forgery vulnerability in meeting-room-booking-system mrbs-code, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Meeting Room Booking System (MRBS) is a PHP-based application for booking meeting rooms. Prior to version 1.12.2, a user-supplied private/local URI can be made to be fetched without checks. Version 1.12.2 contains a fix. No known workarounds are available.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-46382?


## How do I fix CVE-2026-46382?

No fix has been published for CVE-2026-46382 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46382 being exploited?

There is no known exploitation of CVE-2026-46382 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46382 and fix it if it is affected.

What it is: CVE-2026-46382 is a high-severity server-side request forgery vulnerability in meeting-room-booking-system mrbs-code, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46382 in the wild and no public exploit code.

Affected product: meeting-room-booking-system mrbs-code. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46382/ (Markdown: https://insights.sbomify.com/CVE-2026-46382/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46382
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46382
- OSV: https://osv.dev/vulnerability/CVE-2026-46382

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46382/
Summaries are generated and may contain mistakes; the official description above is the record.