# CVE-2026-129134: MRBS before 1.13.0 Password Reset Poisoning via Host Header Injection


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-2x54-phff-qr64, GHSA-73cv-hx7f-9v27

## What is CVE-2026-129134?

CVE-2026-129134 is a high-severity vulnerability in meeting-room-booking-system mrbs-code, published on 13 Nov 2026. 

### Official description

MRBS before 1.13.0 contains a password reset poisoning vulnerability that allows unauthenticated attackers to redirect reset links by forging the Host header when $url_base is unset. Attackers can request a reset for a victim so AuthDb::notifyUser() emails a link pointing to their host, capturing the reset key when opened to take over accounts including administrators.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

1 open source package ship an affected version, including meeting-room-booking-system/mrbs-code.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `meeting-room-booking-system/mrbs-code` | GitHub | `pkg:github/meeting-room-booking-system/mrbs-code` | All versions | 1.13.0 |

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

Upgrade meeting-room-booking-system/mrbs-code to 1.13.0 or later.

## Is CVE-2026-129134 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129134 is a high-severity vulnerability in meeting-room-booking-system mrbs-code, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129134 in the wild and no public exploit code.

Affected packages and fixed versions:
- meeting-room-booking-system/mrbs-code (GitHub): affected all versions; fixed in 1.13.0

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-129134/ (Markdown: https://insights.sbomify.com/CVE-2026-129134/index.md)
```

## Sources

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

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